From: coly <colyli@gmail.com>
To: Badari Pulavarty <pbadari@gmail.com>
Cc: linux-ext4 <linux-ext4@vger.kernel.org>
Subject: Re: which kernel version should I submit patch ?
Date: Thu, 03 May 2007 13:05:37 +0800 [thread overview]
Message-ID: <1178168737.30661.4.camel@colyT43.site> (raw)
In-Reply-To: <1178147812.24273.26.camel@dyn9047017100.beaverton.ibm.com>
Badari:
Thanks, maybe Ted's tree is a good choice :-)
Best regards.
Coly
在 2007-05-02三的 16:16 -0700，Badari Pulavarty写道：
> On Thu, 2007-05-03 at 02:13 +0800, coly wrote:
> > Hi, list.
> >
> > I find these days 2.6.21 released. If I will submit patches for ext4dev,
> > should I generate the patch against 2.6.21 ?
>
>
> If you find a bug in ext4 on 2.6.21 - yes, generate against 2.6.21.
>
> Make sure its not already fixed in -mm or Ted's ext4 tree.
>
> http://www2.kernel.org/pub/linux/kernel/people/tytso/ext4-patches/
>
> Thanks,
> Badari
>
prev parent reply other threads:[~2007-05-03 5:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-02 18:13 which kernel version should I submit patch ? coly
2007-05-02 23:16 ` Badari Pulavarty
2007-05-03 5:05 ` coly [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=1178168737.30661.4.camel@colyT43.site \
--to=colyli@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=pbadari@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).