public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Millan <rmh@aybabtu.com>
To: Bron Gondwana <brong@fastmail.fm>
Cc: The development of GRUB 2 <grub-devel@gnu.org>,
	The development of BTRFS <linux-btrfs@vger.kernel.org>,
	Chris Mason <chris.mason@oracle.com>,
	Ric Wheeler <rwheeler@redhat.com>
Subject: Re: grub-0.97: btrfs multidevice  support [PATCH]
Date: Fri, 25 Sep 2009 16:09:51 +0200	[thread overview]
Message-ID: <20090925140951.GA6318@thorin> (raw)
In-Reply-To: <20090924223810.GA2638@brong.net>

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:
> > 
> > Hi Edward,
> > 
> > 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.  Mainly because you deprecated GRUB Legacy[tm]
> well before GRUB 2 was usable.
> 
> (you in the generic sense of the GRUB project here)
> 
> 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.
> 
> Sometimes you have to maintain crappy code because people out there depend
> on it.  And we thank those who step up and do it rather than throw their
> hands up and pretend it doesn't need doing!

I'm not telling anyone what should or shouldn't work with.  But if you want to
work on a branch we consider deprecated, please do it elsewhere.  Discussion
regarding GRUB Legacy is off-topic in this list.

Thanks

-- 
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:[~2009-09-25 14:09 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 [this message]
2009-09-25 14:16       ` Ric Wheeler
2009-09-25 15:22         ` Robert Millan
2009-09-25 15:01       ` Colin Watson
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=20090925140951.GA6318@thorin \
    --to=rmh@aybabtu.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