[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH] save_env variable_name=value
From: |
Robert Millan |
Subject: |
Re: [PATCH] save_env variable_name=value |
Date: |
Sat, 12 Sep 2009 14:43:50 +0200 |
User-agent: |
Mutt/1.5.18 (2008-05-17) |
On Fri, Sep 11, 2009 at 05:43:06PM -0400, Pavel Roskin wrote:
> On Thu, 2009-09-03 at 17:08 +0200, Robert Millan wrote:
>
> > Pavel, please comment on this when you can. It seems to me that doing it
> > in grub-mkconfig would require less ad-hoc code in loadenv.mod and make it
> > more efficient.
>
> I don't see how grub-mkconfig could compensate for a missing feature in
> save_env. Perhaps I'm missing the context here.
Instead of issuing:
save_env variable=value
grub-mkconfig can issue:
set variable=value
save_env
which doesn't need additional logic in save_env.
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you to remove your data and not access it at all."
- [PATCH] save_env variable_name=value, Colin Watson, 2009/09/02
- Re: [PATCH] save_env variable_name=value, Robert Millan, 2009/09/03
- Re: [PATCH] save_env variable_name=value, Colin Watson, 2009/09/03
- Re: [PATCH] save_env variable_name=value, Robert Millan, 2009/09/03
- Re: [PATCH] save_env variable_name=value, Pavel Roskin, 2009/09/11
- Re: [PATCH] save_env variable_name=value,
Robert Millan <=
- Re: [PATCH] save_env variable_name=value, Colin Watson, 2009/09/12
- Re: [PATCH] save_env variable_name=value, address@hidden, 2009/09/12
- Re: [PATCH] save_env variable_name=value, Pavel Roskin, 2009/09/13