From: "Vesa Jääskeläinen" <chaac@nic.fi>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [RFC] rename update-grub to update-grubcfg
Date: Wed, 17 Sep 2008 17:31:44 +0300 [thread overview]
Message-ID: <48D114D0.8040509@nic.fi> (raw)
In-Reply-To: <20080917135632.GA23010@thorin>
Robert Millan wrote:
> On Mon, Sep 15, 2008 at 09:14:03PM +0300, Vesa Jääskeläinen wrote:
>> Felix Zielcke wrote:
>>> Attached is now a patch which renames it to grub-mkconf and prints it to
>>> stdout instead of grub.cfg file.
>>> I kept the Found kernel/initrd etc. stuff to stderr, but maybe this
>>> should be removed ?
>> mkconf?
>>
>> Could it be a bit more verbose ;)... if we are to go path of
>> grub-mkconfig (or even grub-make-config).
>
> I like my bikeshed with "config" in it, too. ;-)
>
>> Thou I prefer myself
>> grub-update-config being more descriptive on what it does.
>
> With the proposed behaviour, it wouldn't be "updating" anything. That depends
> on how it is used (one could just want to generate grub.cfg a single time, or
> so).
Well... grub-mkconfig then ?
>> grub-update-config --out <file> could be easily used to override where
>> to save the generate configuration file.
>
> Why not '-o' for consistency with grub-mk*image ?
That is fine for me.
next prev parent reply other threads:[~2008-09-17 14:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-04 12:22 [RFC] rename update-grub to update-grubcfg Felix Zielcke
2008-09-04 13:56 ` Pavel Roskin
2008-09-04 17:38 ` Vesa Jääskeläinen
2008-09-04 17:50 ` Felix Zielcke
2008-09-04 19:45 ` Robert Millan
2008-09-15 17:56 ` Felix Zielcke
2008-09-15 18:14 ` Vesa Jääskeläinen
2008-09-17 13:56 ` Robert Millan
2008-09-17 14:31 ` Vesa Jääskeläinen [this message]
2008-09-17 15:24 ` Felix Zielcke
2008-09-24 9:49 ` Robert Millan
2008-09-24 11:04 ` Felix Zielcke
2008-09-24 13:22 ` Robert Millan
2008-09-24 13:34 ` Felix Zielcke
2008-09-24 13:54 ` Robert Millan
2008-09-29 14:57 ` Felix Zielcke
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=48D114D0.8040509@nic.fi \
--to=chaac@nic.fi \
--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.