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: Sun, 27 Sep 2009 12:38:55 +0200	[thread overview]
Message-ID: <20090927103855.GA22813@thorin> (raw)
In-Reply-To: <20090924223810.GA2638@brong.net>

On Fri, Sep 25, 2009 at 08:38:10AM +1000, Bron Gondwana wrote:
> 
> 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!

Btw, I just wanted to add that although we decide to focus on the codebase
that has a future, it doesn't bother me at all that GRUB Legacy is useful to
others.  We made it free software so that it enables as many users as possible
to use their computer in freedom, and so that distributors can adopt it
despite our disrecommendation.

I don't regret that they have the practical means to disagree with us and take
a different path.  It's precisely the freedom we wanted them to benefit from!

Nevertheless, grub-devel is a mailing list for coordination of GRUB 2
development.  Most of us are volunteers and our time is quite limited, so
bringing up GRUB Legacy development here is at best a distraction.  I'll
appreciate if you won't do that anymore.

Thanks for listening

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

      parent reply	other threads:[~2009-09-27 10:38 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
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 [this message]

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=20090927103855.GA22813@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