public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu
To: Eric Anopolsky <erpo41@gmail.com>
Cc: Adrian Bunk <bunk@kernel.org>,
	sct@redhat.com, akpm@linux-foundation.org, adilger@clusterfs.com,
	linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [2.6.24 patch] let EXT4DEV_FS depend on BROKEN
Date: Fri, 04 Jan 2008 00:41:37 -0500	[thread overview]
Message-ID: <11223.1199425297@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Wed, 02 Jan 2008 13:51:32 PST." <1199310692.5786.53.camel@dione>

[-- Attachment #1: Type: text/plain, Size: 421 bytes --]

On Wed, 02 Jan 2008 13:51:32 PST, Eric Anopolsky said:

> their own kernels in the first place. IMHO, it's reasonable to expect
> the small minority of Linux users who want to compile their own kernels
> to learn that "EXPERIMENTAL" means something.

And what, exactly, does it mean, given that there's a bunch of stuff that's
tagged EXPERIMENTAL that's more solid/tested than a lot of stuff that *isn't*
marked with it?

[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]

  reply	other threads:[~2008-01-04  5:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-02  1:32 [2.6.24 patch] let EXT4DEV_FS depend on BROKEN Adrian Bunk
2008-01-02 17:41 ` Andreas Dilger
2008-01-02 19:51   ` Adrian Bunk
2008-01-02 21:51     ` Eric Anopolsky
2008-01-04  5:41       ` Valdis.Kletnieks [this message]
2008-01-02 22:43     ` Eric Sandeen
2008-01-02 20:40   ` Alan Cox
2008-01-02 18:26 ` Diego Calleja
2008-01-02 21:16   ` Adrian Bunk
2008-01-02 21:21     ` Alan Cox
2008-01-02 21:31     ` Trond Myklebust

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=11223.1199425297@turing-police.cc.vt.edu \
    --to=valdis.kletnieks@vt.edu \
    --cc=adilger@clusterfs.com \
    --cc=akpm@linux-foundation.org \
    --cc=bunk@kernel.org \
    --cc=erpo41@gmail.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sct@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox