All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vladimir 'phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Grub get and set efi variables
Date: Wed, 2 Dec 2015 14:05:10 +0100	[thread overview]
Message-ID: <CAEaD8JMO4S5oti15hOSu=VyiWkgpLs7Jqfu05WW0-5cybnuVUw@mail.gmail.com> (raw)
In-Reply-To: <CAA91j0X8f5pcMwha3OmW4ca9gMY53PcuT7szHr088Jt2QKW_0A@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1327 bytes --]

Le 2 déc. 2015 2:01 PM, "Andrei Borzenkov" <arvidjaar@gmail.com> a écrit :

>

> On Wed, Dec 2, 2015 at 3:53 PM, Ignat Korchagin <ignat@cloudflare.com>
wrote:

> > Let's add utf16 later then (if needed). I also noticed a typo in one

> > error string in my above patch (it was checking that command receives

> > one argument, but prints that two arguments expected), so here is the

> > updated one.

> >

>

> It is much more difficult to remove anything than to add it later.

> Unless we have use case right now, I'd skip it.

>

> > So, finally, should I remove the "raw" parser (as per Vladimir's

> > request). Personally, I would keep it. It might be useful to modify

> > the hexdump command, that it can dump the contents of a variable. Then

> > those pieces will fit together: storing raw value in the variable and

> > examining it with hexdump cmd.

> >

>

> hexdump does not support showing variable if that is what you mean. By

> the same logic, unless we have current use case we probably should not

> add it initially.

>

We don't even support storing non-utf8 in a variable. So please skip it

> _______________________________________________

> Grub-devel mailing list

> Grub-devel@gnu.org

> https://lists.gnu.org/mailman/listinfo/grub-devel

[-- Attachment #2: Type: text/html, Size: 1769 bytes --]

  reply	other threads:[~2015-12-02 13:05 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-03 19:39 Grub get and set efi variables Mat Troi
2015-11-03 20:12 ` SevenBits
2015-11-03 23:05   ` Mat Troi
2015-11-04  5:38     ` Andrei Borzenkov
2015-11-05 18:25       ` SevenBits
2015-11-06  2:00         ` Ignat Korchagin
2015-11-11 18:09           ` Andrei Borzenkov
2015-11-13 19:34             ` Ignat Korchagin
2015-11-13 19:42               ` Ignat Korchagin
2015-11-14  4:03                 ` Andrei Borzenkov
2015-11-17 11:48                   ` Ignat Korchagin
2015-11-29  8:57                     ` Andrei Borzenkov
2015-11-24 19:23                   ` Mat Troi
2015-11-24 20:48                     ` Seth Goldberg
2015-11-27 14:07                   ` Vladimir 'φ-coder/phcoder' Serbinenko
2015-11-27 14:25                     ` Ignat Korchagin
2015-11-29  9:00                       ` Andrei Borzenkov
2015-12-02 12:53                         ` Ignat Korchagin
2015-12-02 13:00                           ` Andrei Borzenkov
2015-12-02 13:05                             ` Vladimir 'phcoder' Serbinenko [this message]
2015-12-02 14:52                               ` Ignat Korchagin
2015-12-03 16:43                                 ` Andrei Borzenkov
2015-12-03 17:19                                   ` Ignat Korchagin
2015-12-09 14:42                                     ` Ignat Korchagin
2015-12-12  8:36                                     ` Andrei Borzenkov
2015-12-14 11:08                                       ` Ignat Korchagin
2015-12-14 11:17                                         ` Ignat Korchagin
2016-01-29 16:25                                           ` Ignat Korchagin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAEaD8JMO4S5oti15hOSu=VyiWkgpLs7Jqfu05WW0-5cybnuVUw@mail.gmail.com' \
    --to=phcoder@gmail.com \
    --cc=grub-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.