All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: grub-0.97/btrfs: the files fsys_btrfs.c, btrfs.h
Date: Sat, 25 Jul 2009 18:14:17 +0200	[thread overview]
Message-ID: <20090725161417.GE12326@thorin> (raw)
In-Reply-To: <4A675D2F.3080707@redhat.com>

On Wed, Jul 22, 2009 at 08:40:47PM +0200, Edward Shishkin wrote:
>>> Anyway, nice to see that you work on btrfs for grub.
>>> But grub-legacy is totally dead now, it would be better if you would put
>>> your efforts into grub2.
>>>     
>
> Mm.. I am not an individual contributor.
> I work for RHEL and Fedora, which is on grub-0.97 for now..

Hi Edward,

GRUB Legacy is free software, and we're glad that it is useful to RHEL and
Fedora, but please understand that it is not currently supported by us.  It'd
be in Red Hat's best interest to contemplate a transition to GRUB 2, which is
where the development effort is moving towards nowadays.

Debian and Ubuntu have already committed to this goal.

-- 
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-07-25 16:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-22 16:41 grub-0.97/btrfs: the files fsys_btrfs.c, btrfs.h Edward Shishkin
2009-07-22 17:04 ` Felix Zielcke
2009-07-22 17:12   ` Vladimir 'phcoder' Serbinenko
2009-07-22 17:31     ` Edward Shishkin
2009-07-22 18:40     ` Edward Shishkin
2009-07-25 16:14       ` Robert Millan [this message]
2009-07-29 14:57         ` Edward Shishkin
  -- strict thread matches above, loose matches on Subject: below --
2009-07-22 16:03 Edward Shishkin

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=20090725161417.GE12326@thorin \
    --to=rmh@aybabtu.com \
    --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.