From: Matthias Andree <matthias.andree@gmx.de>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Matthias Andree <matthias.andree@gmx.de>,
Grzegorz Kulewski <kangur@polcom.net>,
Diego Calleja <diegocg@gmail.com>,
arjan@infradead.org, caleb@calebgray.com,
linux-kernel@vger.kernel.org
Subject: Re: Reiser4 Inclusion
Date: Tue, 18 Jul 2006 22:47:18 +0200 [thread overview]
Message-ID: <20060718204718.GD18909@merlin.emma.line.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0607180951480.16615@yvahk01.tjqt.qr>
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
next prev parent reply other threads:[~2006-07-18 20:47 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-17 3:02 Caleb Gray
2006-07-17 9:25 ` Arjan van de Ven
2006-07-17 11:48 ` Grzegorz Kulewski
2006-07-17 11:57 ` Alexander Gran
2006-07-17 14:06 ` Diego Calleja
2006-07-17 14:31 ` Grzegorz Kulewski
2006-07-17 15:51 ` Matthias Andree
2006-07-18 7:59 ` Jan Engelhardt
2006-07-18 20:47 ` Matthias Andree [this message]
2006-07-19 1:19 ` Joshua Hudson
2006-07-19 9:27 ` Tilman Schmidt
2006-07-19 11:00 ` Krzysztof Halasa
2006-07-19 11:03 ` Pekka Enberg
2006-07-19 15:32 ` Tilman Schmidt
2006-07-19 19:04 ` Valdis.Kletnieks
2006-07-19 19:12 ` Tilman Schmidt
2006-07-19 20:09 ` Valdis.Kletnieks
2006-07-19 22:36 ` Tilman Schmidt
2006-07-19 20:29 ` Jeff V. Merkey
2006-07-19 22:01 ` Matthias Andree
2006-07-19 22:34 ` Helge Hafting
2006-07-17 15:52 ` gmu 2k6
2006-07-17 15:57 ` Alexander Gran
2006-07-17 19:01 ` Horst von Brand
2006-07-17 15:13 ` Jeff Anderson-Lee
2006-07-17 15:56 ` Matthias Andree
2006-07-17 20:48 ` Erik Mouw
2006-07-18 0:49 ` Jeff Dike
2006-07-18 11:43 ` Christoph Hellwig
2006-07-17 9:44 ` Patrick McFarland
2006-07-17 11:07 ` Diego Calleja
2006-07-17 14:38 ` Alex Riesen
2006-07-17 18:05 ` Valdis.Kletnieks
2006-07-18 23:10 ` Nix
2006-07-19 6:56 ` Reiser4 ACLs Marc Perkel
2006-07-19 15:03 ` Jan Engelhardt
2006-07-17 22:34 Reiser4 Inclusion linux
[not found] <06Jul25.011533edt.35900@gpu.utcc.utoronto.ca>
2006-07-30 22:02 ` Tilman Schmidt
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=20060718204718.GD18909@merlin.emma.line.org \
--to=matthias.andree@gmx.de \
--cc=arjan@infradead.org \
--cc=caleb@calebgray.com \
--cc=diegocg@gmail.com \
--cc=jengelh@linux01.gwdg.de \
--cc=kangur@polcom.net \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®