From: Bron Gondwana <brong@fastmail.fm>
To: Miguel Sousa Filipe <miguel.filipe@gmail.com>
Cc: btrfs-devel@oss.oracle.com, linux-btrfs@vger.kernel.org
Subject: Re: BTRFS and old kernels.
Date: Sun, 6 Apr 2008 10:57:12 +1000 [thread overview]
Message-ID: <20080406005712.GA24967@brong.net> (raw)
In-Reply-To: <f058a9c30804051213j4276cc88j92a8222dd4115e39@mail.gmail.com>
On Sat, Apr 05, 2008 at 08:13:47PM +0100, Miguel Sousa Filipe wrote:
> My question is, is there sill interestest in having btrfs compatible
> with older kernels (like, 2.6.20 or 2.6.18)?
> I'll post (or repost) patches that I need for btrfs-unstable to
> build/work on this ppc system of mine.
It sort of depends who you ask. Personally, I see value in being
compatible with as wide range of kernels as possible in a development
filesystem that you want people to be testing. But then I'm not
doing any btrfs development, so I don't count for much.
Other people, well - Christoph Hellwig had this to say a little
while back in <20080207044835.GC4140@lst.de> (rewrapped):
On Wed, Feb 06, 2008 at 05:14:51PM -0500, Jeff Mahoney wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Kernels prior to 2.6.19 don't export file_ra_state_init().
> This patch adds the file_ra_state_init() from 2.6.18.
Please put this somewhere else, a separate file and hopefully
only in your backports tree. This is kernels from stoneage
after all, not just one or two revisions back.
Bron ( not being particularly helpful or even answering your
question really )
next prev parent reply other threads:[~2008-04-06 0:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-05 19:13 BTRFS and old kernels Miguel Sousa Filipe
2008-04-06 0:57 ` Bron Gondwana [this message]
2008-04-06 1:31 ` Bron Gondwana
2008-04-07 12:54 ` Chris Mason
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=20080406005712.GA24967@brong.net \
--to=brong@fastmail.fm \
--cc=btrfs-devel@oss.oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=miguel.filipe@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.