All of lore.kernel.org
 help / color / mirror / Atom feed
From: Felix Zielcke <fzielcke@z-51.de>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [RFC] rename update-grub to update-grubcfg
Date: Thu, 04 Sep 2008 19:50:19 +0200	[thread overview]
Message-ID: <1220550619.18782.33.camel@fz.local> (raw)
In-Reply-To: <48C01D0C.1000300@nic.fi>

Am Donnerstag, den 04.09.2008, 20:38 +0300 schrieb Vesa Jääskeläinen:
> > If you are going to rename it, please use a name starting with "grub",
> > not with "update".  Debian is free to provide a wrapper starting with
> > "update".
> 
> How about grub-update-config ?

I have now read over the old thread, I was just too lazy first and it
was half a year old anyway.
Okuji suggested grub-update-config too.

Personally as a user I would still prefer update-grub* and even
install-grub
Because you are update'ing grub's config and installing grub
grub-mkdevicemap and grub-probe make sense that way
make device map for grub
probe for a grub device

Though yes for consistency everything grub-* would be better.
It's just like Robert already said on the old thread, Debian people know
it as update-grub from grub-legacy.

So there should be some update-grub wrapper/stub for a while, with a
hint that it's deprecated now.

For Debian it doestn't matter much how it gets changed, the problem is
more the change itself ;)
And I share Robert's opinion, that we (as in: the 2 active GRUB Debian
Maintainers) shouldn't diverge much from upstream (i.e. you ;) like it
was done on grub-legacy.

-- 
Felix Zielcke




  reply	other threads:[~2008-09-04 17:50 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 [this message]
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
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=1220550619.18782.33.camel@fz.local \
    --to=fzielcke@z-51.de \
    --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.