mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Pekka Enberg" <penberg@cs.helsinki.fi>
To: "Adrian Bunk" <bunk@kernel.org>
Cc: "Willy Tarreau" <w@1wt.eu>, "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:44:12 +0300	[thread overview]
Message-ID: <84144f020805030244y44313fdl17cee6fa38bfd690@mail.gmail.com> (raw)
In-Reply-To: <20080503091111.GH5838@cs181133002.pp.htv.fi>

Hi Adrian,

On Sat, May 3, 2008 at 12:11 PM, Adrian Bunk <bunk@kernel.org> wrote:
> > 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.

I think ext4 already set the precedent that you _can_ do development
within the 2.6 series, no?

  parent reply	other threads:[~2008-05-03  9:44 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
2008-05-03  9:18                 ` Willy Tarreau
2008-05-03  9:37                   ` Adrian Bunk
2008-05-03  9:44                 ` Pekka Enberg [this message]
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=84144f020805030244y44313fdl17cee6fa38bfd690@mail.gmail.com \
    --to=penberg@cs.helsinki.fi \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=bunk@kernel.org \
    --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®