[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20060718204718.GD18909@merlin.emma.line.org>
Date: Tue, 18 Jul 2006 22:47:18 +0200
From: Matthias Andree <matthias.andree@....de>
To: Jan Engelhardt <jengelh@...ux01.gwdg.de>
Cc: Matthias Andree <matthias.andree@....de>,
Grzegorz Kulewski <kangur@...com.net>,
Diego Calleja <diegocg@...il.com>, arjan@...radead.org,
caleb@...ebgray.com, linux-kernel@...r.kernel.org
Subject: Re: Reiser4 Inclusion
Jan Engelhardt schrieb am 2006-07-18:
> Because that patch pokes into some files outside fs/reiser4, giving a hard time
> with rejects for the novice user. The linux kernel is a huge codebase, and
> I have, for example, less clue of mm/ than of fs/.
>
> I was very happy to see that
> ftp://ftp.namesys.com/pub/reiser4-for-2.6/2.6.16/reiser4-for-2.6.16-4.patch.gz
> worked well on 2.6.17 and 2.6.17.x, but it already stopped patching again
> on 2.6.18-rc1. The next newer version of reiser4 is for -mm, which is not
Sorry, none of the kernel's business.
ISTR they have been asked to review/justify the bits outside fs/reiser4
and feed them separately where valuable and otherwise move or drop.
> so useful for me. If namesys provided reiser4 patches for every vanilla out
> there (possibly including -rc's, but that's just extra sugar), that would
> be great, but I cannot force them to do so; people may have better things
> to do than packaging up r4 whenever there is a linux tarball release.
And probably kernel hackers have better things to do than keeping that
code building if they don't mean to support it. This touches the "stable
APIs" can of worms again, so let's stop here before it springs open.
-
Matthias Andree
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists