From: Colin Watson <cjwatson@ubuntu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Cc: Bron Gondwana <brong@fastmail.fm>,
Ric Wheeler <rwheeler@redhat.com>,
The development of BTRFS <linux-btrfs@vger.kernel.org>,
Chris Mason <chris.mason@oracle.com>
Subject: Re: grub-0.97: btrfs multidevice support [PATCH]
Date: Fri, 25 Sep 2009 16:01:36 +0100 [thread overview]
Message-ID: <20090925150136.GQ13423@riva.ucam.org> (raw)
In-Reply-To: <20090925140951.GA6318@thorin>
On Fri, Sep 25, 2009 at 04:09:51PM +0200, Robert Millan wrote:
> On Fri, Sep 25, 2009 at 08:38:10AM +1000, Bron Gondwana wrote:
> > On Thu, Sep 24, 2009 at 10:21:46PM +0200, Robert Millan wrote:
> > > I'm sorry but GRUB Legacy is not maintained. At least not by us; we've
> > > deprecated it in favour of GRUB 2.
> > >
> > > It is also being abandoned by distributors, so I wouldn't recommend that you
> > > put any effort in developing for it.
> >
> > You've been spouting this line for years, and yet my Ubuntu 10.4 machine
> > uses, guess what, GRUB 1.
I assume you typoed, since there's no such thing as Ubuntu 10.4 yet.
When there is (well, 10.04 anyway), it will use GRUB 2 by default.
> > Edward - please do continue to develop patches for GRUB 1 (the one that
> > still actually works plenty well enough for lots of people) and ignore the
> > naysayers who are happy to throw out backwards compatibility.
It would be great if somebody could take up Edward's work and port it to
GRUB 2. If nobody else does then I'd be interested in doing so myself,
although I will not be able to start for a month or two from now.
Robert is working hard on making GRUB 2 usable, and is just advising
Edward that, right now, there is no upstream for GRUB Legacy who could
either accept or usefully comment on his patch. It would of course be
possible for some people (presumably mostly the distributors who rely on
it) to get together and declare themselves the new upstream for GRUB
Legacy, but most of the people who might be interested in such things
seem to have either lost interest or thrown their weight behind GRUB 2
upstream. Certainly this distributor right here is in the latter camp as
it seems much more likely to produce a result that meets our needs in
the end. (Plus, I think such a revitalised upstream would be a caretaker
at best, and wouldn't really be able to effectively work on some of the
major issues that have dogged distributors of GRUB Legacy for years
without reinventing the wheel of GRUB 2.)
This isn't naysaying those people who post patches for GRUB Legacy - but
given the reality that nobody is maintaining GRUB Legacy upstream right
now, which is better, to have your patch ignored or to receive a note
saying that it's against an unmaintained target? I'd go for not being
ignored any day.
--
Colin Watson [cjwatson@ubuntu.com]
next prev parent reply other threads:[~2009-09-25 15:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-24 19:01 grub-0.97: btrfs multidevice support [PATCH] Edward Shishkin
2009-09-24 20:21 ` Robert Millan
2009-09-24 22:38 ` Bron Gondwana
2009-09-25 14:09 ` Robert Millan
2009-09-25 14:16 ` Ric Wheeler
2009-09-25 15:22 ` Robert Millan
2009-09-25 15:01 ` Colin Watson [this message]
2009-09-25 23:35 ` Joel Becker
2009-09-25 23:47 ` Bron Gondwana
2009-09-27 3:29 ` Peng Tao
2009-09-27 10:18 ` Robert Millan
2009-09-28 1:53 ` Peng Tao
2009-09-28 7:47 ` Vladimir 'phcoder' Serbinenko
2009-09-28 15:36 ` Chris Mason
2009-10-02 20:48 ` Robert Millan
2009-09-27 10:38 ` 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=20090925150136.GQ13423@riva.ucam.org \
--to=cjwatson@ubuntu.com \
--cc=brong@fastmail.fm \
--cc=chris.mason@oracle.com \
--cc=grub-devel@gnu.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=rwheeler@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox