From: "Felix Zielcke" <fzielcke@z-51.de>
To: "'The development of GRUB 2'" <grub-devel@gnu.org>
Subject: RE: rename grub to grub-legacy ?
Date: Thu, 9 Oct 2008 17:58:38 +0200 [thread overview]
Message-ID: <001801c92a27$e5a61dd0$b0f25970$@de> (raw)
In-Reply-To: <1223566611.28088.30.camel@dv>
> -----Original Message-----
> From: grub-devel-bounces+fzielcke=z-51.de@gnu.org [mailto:grub-devel-
> bounces+fzielcke=z-51.de@gnu.org] On Behalf Of Pavel Roskin
> Sent: Thursday, October 09, 2008 5:37 PM
> To: The development of GRUB 2
> Subject: Re: rename grub to grub-legacy ?
>
> I believe Okuji wanted to use a different naming scheme, that would put
> "grub2" or "grub-legacy" above trunk. You may want to check it to
> avoid
> moving things twice.
Right, there was already a topic about the SVN structure I totally forgot about:
http://lists.gnu.org/archive/html/grub-devel/2008-07/msg00248.html
> All the above notwithstanding, I'm still skeptical about the whole
> moving idea based on my experience with other projects. Repositories
> are for developers and should be used in the way that minimizes
> troubles
> for developers rather than reduces the entry barrier for newbies.
I think grub-legacy is dead from developer POV or am I wrong?
But you're right if we change things then we should do this only once,
so I'm now not that sure what to do now.
next prev parent reply other threads:[~2008-10-09 15:58 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
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 [this message]
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='001801c92a27$e5a61dd0$b0f25970$@de' \
--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.