All of lore.kernel.org
 help / color / mirror / Atom feed
From: Edward Shishkin <edward.shishkin@gmail.com>
To: "Vladimir 'phcoder' Serbinenko" <phcoder@gmail.com>
Cc: The development of GRUB 2 <grub-devel@gnu.org>,
	linux-btrfs@vger.kernel.org
Subject: Re: grub-0.97/btrfs: the files fsys_btrfs.c, btrfs.h
Date: Wed, 22 Jul 2009 19:31:58 +0200	[thread overview]
Message-ID: <4A674D0E.1040900@gmail.com> (raw)
In-Reply-To: <d7ead6de0907221012h6909ba16u6fa301da142028fe@mail.gmail.com>

Vladimir 'phcoder' Serbinenko wrote:
> On Wed, Jul 22, 2009 at 7:04 PM, Felix Zielcke<fzielcke@z-51.de> wrote:
>   
>> Am Mittwoch, den 22.07.2009, 18:41 +0200 schrieb Edward Shishkin:
>>
>> Hi Edward,
>>
>>     

Hello.

>>> (CC linux-btrfs mailing list)
>>>       
>> Uhm there is no CC?
>> I'm unsure now if I should CC it or not.
>>     
> Edward had a problem sending to our list because grub-devel is
> subscriber-only list. Let's CC linux-btrfs
>   
>> 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..

> I would be happy to assist with this. I already have such experience
> porting zfs from grub-solaris to grub2
>   

It would be fine..

Thanks,
Edward.

  reply	other threads:[~2009-07-22 17:31 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 [this message]
2009-07-22 18:40     ` Edward Shishkin
2009-07-25 16:14       ` Robert Millan
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=4A674D0E.1040900@gmail.com \
    --to=edward.shishkin@gmail.com \
    --cc=grub-devel@gnu.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=phcoder@gmail.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.