All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Cc: "Yoshinori K. Okuji" <okuji@enbug.org>
Subject: Re: rename grub to grub-legacy ?
Date: Fri, 1 Aug 2008 17:39:34 +0200	[thread overview]
Message-ID: <20080801153934.GA20000@thorin> (raw)
In-Reply-To: <873aloixfu.fsf@xs4all.nl>

On Fri, Aug 01, 2008 at 05:09:41PM +0200, Marco Gerards wrote:
> Hi,
> 
> Robert Millan <rmh@aybabtu.com> writes:
> 
> > What would you think of renaming grub to grub-legacy in SVN ?
> >
> > I think it'd help send a strong message that we consider this a legacy branch
> > and is not open for further development.
> 
> This is fine for me.  Can you do this assuming Okuji and other
> developers do not have strong objections?

Adding Okuji to CC, just to make sure he reads it.

-- 
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."



  reply	other threads:[~2008-08-01 15:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-01 14:48 rename grub to grub-legacy ? Robert Millan
2008-08-01 15:09 ` Marco Gerards
2008-08-01 15:39   ` Robert Millan [this message]
2008-08-03 20:04     ` Robert Millan
2008-08-03 23:19       ` Gregg Levine
2008-08-04  5:06       ` Pavel Roskin
2008-10-07 17:36     ` Felix Zielcke
2008-10-07 19:24       ` Yoshinori K. Okuji
2008-10-09  9:53         ` Felix Zielcke
2008-10-09 15:36           ` Pavel Roskin
2008-10-09 15:58             ` Felix Zielcke
2008-10-10 22:06               ` Pavel Roskin
2008-10-12  1:53               ` Gregg C Levine
2008-11-29 17:02             ` Robert Millan
2008-08-01 15:15 ` Gregg C Levine

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=20080801153934.GA20000@thorin \
    --to=rmh@aybabtu.com \
    --cc=grub-devel@gnu.org \
    --cc=okuji@enbug.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.