From: Ted Ts'o <tytso@mit.edu>
To: puru sothaman <r.puru@yahoo.co.in>
Cc: linux-ext4@vger.kernel.org
Subject: Re: backporting ext4 to 2.6.27
Date: Mon, 9 May 2011 12:05:48 -0400 [thread overview]
Message-ID: <20110509160548.GC19811@thunk.org> (raw)
In-Reply-To: <86980.98056.qm@web95210.mail.in2.yahoo.com>
On Mon, May 09, 2011 at 08:16:09PM +0530, puru sothaman wrote:
> Hi,
>
> I am using 2.6.27.18 kernel.Currently the ext4 support in kernel
>is experimental version.I need a stable version ext4 patches for the
>above kernel.Can anyone help me in backporting the stable ext4
>patches for 2.6.27 kernel.
Backporting patches to an ancient kernel like 2.6.27 is one of those
painful things that get done by people who are paid to do so --- it's
hard to find volunteers willing to do such a grungy task....
- Ted
next prev parent reply other threads:[~2011-05-09 16:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-09 14:46 (unknown) puru sothaman
2011-05-09 16:05 ` Ted Ts'o [this message]
2011-05-09 22:52 ` backporting ext4 to 2.6.27 Greg Freemyer
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=20110509160548.GC19811@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=r.puru@yahoo.co.in \
/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).