From: Robert Millan <rmh@aybabtu.com>
To: Ric Wheeler <rwheeler@redhat.com>
Cc: The development of GRUB 2 <grub-devel@gnu.org>,
Bron Gondwana <brong@fastmail.fm>,
Chris Mason <chris.mason@oracle.com>,
The development of BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: grub-0.97: btrfs multidevice support [PATCH]
Date: Fri, 25 Sep 2009 17:22:48 +0200 [thread overview]
Message-ID: <20090925152248.GB7197@thorin> (raw)
In-Reply-To: <4ABCD0A9.4040408@redhat.com>
On Fri, Sep 25, 2009 at 07:16:09AM -0700, Ric Wheeler wrote:
>
> That would be rather unusual - we certainly discuss ext2 and ancient file
> systems in our ext development lists.
>
> A lot of distros (and their users) still use grub, just like a lot of
> users still use ext2.
We support ext2 too. And even awfully old things like fat (which is often
used with supposedly modern *cough* EFI).
--
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."
WARNING: multiple messages have this Message-ID (diff)
From: Robert Millan <rmh@aybabtu.com>
To: Ric Wheeler <rwheeler@redhat.com>
Cc: Bron Gondwana <brong@fastmail.fm>,
The development of GRUB 2 <grub-devel@gnu.org>,
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 17:22:48 +0200 [thread overview]
Message-ID: <20090925152248.GB7197@thorin> (raw)
In-Reply-To: <4ABCD0A9.4040408@redhat.com>
On Fri, Sep 25, 2009 at 07:16:09AM -0700, Ric Wheeler wrote:
>
> That would be rather unusual - we certainly discuss ext2 and ancient file
> systems in our ext development lists.
>
> A lot of distros (and their users) still use grub, just like a lot of
> users still use ext2.
We support ext2 too. And even awfully old things like fat (which is often
used with supposedly modern *cough* EFI).
--
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."
next prev parent reply other threads:[~2009-09-25 15:23 UTC|newest]
Thread overview: 27+ 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 19:01 ` 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:09 ` Robert Millan
2009-09-25 14:16 ` Ric Wheeler
2009-09-25 15:22 ` Robert Millan [this message]
2009-09-25 15:22 ` Robert Millan
2009-09-25 15:01 ` Colin Watson
2009-09-25 15:33 ` Felix Zielcke
2009-09-25 23:35 ` Joel Becker
2009-09-25 23:47 ` Bron Gondwana
2009-09-27 3:29 ` Peng Tao
2009-09-27 3:29 ` Peng Tao
2009-09-27 10:18 ` Robert Millan
2009-09-27 10:18 ` Robert Millan
2009-09-28 1:53 ` Peng Tao
2009-09-28 1:53 ` Peng Tao
2009-09-28 7:47 ` Vladimir 'phcoder' Serbinenko
2009-09-28 7:47 ` Vladimir 'phcoder' Serbinenko
2009-09-28 15:36 ` Chris Mason
2009-10-02 20:48 ` Robert Millan
2009-10-02 20:48 ` Robert Millan
2009-09-27 10:38 ` Robert Millan
2009-09-27 10:38 ` Robert Millan
2009-09-24 23:41 ` 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=20090925152248.GB7197@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 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.