From: Adrian Bunk <bunk@kernel.org>
To: Willy Tarreau <w@1wt.eu>
Cc: "Jörn Engel" <joern@logfs.org>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Stephen Rothwell" <sfr@canb.auug.org.au>,
"Andrew Morton" <akpm@linux-foundation.org>,
"David Woodhouse" <dwmw2@infradead.org>,
"Arnd Bergmann" <arnd@arndb.de>,
linux-kernel@vger.kernel.org
Subject: Re: LogFS merge
Date: Sat, 3 May 2008 12:11:11 +0300 [thread overview]
Message-ID: <20080503091111.GH5838@cs181133002.pp.htv.fi> (raw)
In-Reply-To: <20080503070318.GR8474@1wt.eu>
On Sat, May 03, 2008 at 09:03:18AM +0200, Willy Tarreau wrote:
> On Fri, May 02, 2008 at 11:58:33PM +0200, Jörn Engel wrote:
> > On Fri, 2 May 2008 14:39:23 -0700, Linus Torvalds wrote:
> > >
> > > Quite frankly, if that's the case, I'd *much* rather see that worked on
> > > first, so that there aren't any format changes that are already known to
> > > be pending before it even gets merged.
> > >
> > > Would it be at all possible to try to do that, or is it just "too far
> > > out"?
> >
> > Definitely possible. The last similar change happened in December and
> > took until March until I ran out of stupid regressions from it. Most
> > likely there are still some I just haven't found yet.
> >
> > The question is when to draw the line and say "This is useful as-is for
> > a sufficient number of users." I don't have a good answer to it. I
> > certainly expect more changes in the future, including format changes.
> > And if we wait for them all to happen, it won't get merged this decade.
>
> Why not merge it and mark it experimental then ? In fact, this is about
> what you're looking for : reduced merge hassle and more testers.
Andi already answered that one:
"Merging file systems too early can quickly ruin their name and that
taint is hard to ever get rid again then (e.g. happened to JFS)"
And a stable kernel shouldn't be something for getting "more testers",
it should be for tested code ready to be used in production.
What you call "more testers" would be people who try it in production
(e.g. to overcome shortcomings of JFFS2) thinking it was stable.
And no, EXPERIMENTAL in the kernel is not usable for keeping people from
trying known-whacky code.
> Willy
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2008-05-03 9:12 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-02 13:32 Jörn Engel
2008-05-02 14:49 ` Pekka Enberg
2008-05-02 15:31 ` Christoph Hellwig
2008-05-02 20:33 ` Jörn Engel
2008-05-02 16:52 ` Arnd Bergmann
2008-05-02 21:47 ` Jörn Engel
2008-05-02 17:17 ` Linus Torvalds
2008-05-02 20:21 ` Jörn Engel
2008-05-02 20:33 ` Linus Torvalds
2008-05-02 21:31 ` Jörn Engel
2008-05-02 21:39 ` Linus Torvalds
2008-05-02 21:58 ` Jörn Engel
2008-05-03 7:03 ` Willy Tarreau
2008-05-03 9:11 ` Adrian Bunk [this message]
2008-05-03 9:18 ` Willy Tarreau
2008-05-03 9:37 ` Adrian Bunk
2008-05-03 9:44 ` Pekka Enberg
2008-05-03 11:06 ` Adrian Bunk
2008-05-03 17:16 ` Linus Torvalds
2008-05-03 17:59 ` Offtopic to: " David Collier-Brown
2008-05-02 17:29 ` Andi Kleen
2008-05-02 21:34 ` Jörn Engel
2008-05-05 20:31 ` Andrew Morton
2008-05-03 9:29 matthieu castet
2008-05-03 12:00 ` Jörn Engel
2008-05-04 16:20 ` Thomas Gleixner
2008-05-04 18:04 ` Josh Boyer
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=20080503091111.GH5838@cs181133002.pp.htv.fi \
--to=bunk@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=dwmw2@infradead.org \
--cc=joern@logfs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.org \
--cc=w@1wt.eu \
/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®