[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH] save_env variable_name=value
From: |
Colin Watson |
Subject: |
Re: [PATCH] save_env variable_name=value |
Date: |
Sat, 12 Sep 2009 09:16:35 +0100 |
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.
The choices are:
var=value
save_env var
(uglier grub-mkconfig code, smaller core)
save_env var=value
(simpler grub-mkconfig, more code in core)
--
Colin Watson address@hidden
- [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, 2009/09/12
- Re: [PATCH] save_env variable_name=value,
Colin Watson <=
- Re: [PATCH] save_env variable_name=value, address@hidden, 2009/09/12
- Re: [PATCH] save_env variable_name=value, Pavel Roskin, 2009/09/13