From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: RFC: 1.97 roadmap
Date: Thu, 13 Aug 2009 22:21:33 +0200 [thread overview]
Message-ID: <20090813202133.GE22130@thorin> (raw)
In-Reply-To: <4A82B507.6050002@zetam.org>
Hi Yves,
Please could you include plain text in your mail? HTML-only is difficult
to quote (see below)
On Wed, Aug 12, 2009 at 02:26:47PM +0200, Yves Blusseau wrote:
> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
> <html>
> <head>
> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
> </head>
> <body bgcolor="#ffffff" text="#000000">
> Colin Watson a écrit :
> <blockquote cite="mid:20090812084139.GU11691@riva.ucam.org" type="cite">
> <pre wrap="">On Wed, Aug 12, 2009 at 02:43:34AM +0200, Robert Millan wrote:
> </pre>
> <blockquote type="cite">
> <pre wrap="">On Mon, Aug 10, 2009 at 07:10:12PM +0200, Vladimir 'phcoder' Serbinenko wrote:
> </pre>
> <blockquote type="cite">
> <pre wrap="">What about savedefault? Which savedefault way you prefer?
> </pre>
> </blockquote>
> <pre wrap="">I think it would be good to have. But I haven't followed on the savedefault
> discussion, I just know it would build upon the existing envfile support.
> </pre>
> </blockquote>
> <pre wrap=""><!---->
> I thought Vladimir's general approach in
> <a class="moz-txt-link-freetext" href="http://lists.gnu.org/archive/html/grub-devel/2009-06/msg00002.html">http://lists.gnu.org/archive/html/grub-devel/2009-06/msg00002.html</a> was
> just fine (nice and simple, no fancy event handling, builds on existing
> facilities), although I agree with the suggestions from Robert/Pavel
> that the save step should be a single command/function.
> </pre>
> </blockquote>
> I use the vladimir patch in my grub and it work like a charm. I think
> it's a good approach too.<br>
> <br>
> Yves Blusseau<br>
> </body>
> </html>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel
--
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."
next prev parent reply other threads:[~2009-08-13 20:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-10 16:10 RFC: 1.97 roadmap Robert Millan
2009-08-10 17:10 ` Vladimir 'phcoder' Serbinenko
2009-08-12 0:43 ` Robert Millan
2009-08-12 8:41 ` Colin Watson
2009-08-12 8:47 ` Colin Watson
2009-08-12 12:26 ` Yves Blusseau
2009-08-13 20:21 ` Robert Millan [this message]
2009-08-10 18:20 ` Michal Suchanek
2009-08-10 19:51 ` Vladimir 'phcoder' Serbinenko
2009-08-12 11:56 ` Michal Suchanek
2009-08-12 8:35 ` Colin Watson
2009-08-13 20:31 ` Robert Millan
2009-08-13 20:45 ` grub configuration file format change? Seth Goldberg
2009-08-13 21:03 ` Robert Millan
2009-08-13 21:12 ` Seth Goldberg
2009-08-17 12:55 ` Robert Millan
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=20090813202133.GE22130@thorin \
--to=rmh@aybabtu.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.