From: "Justin T. Gibbs" <Justin_Gibbs@adaptec.com>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: [Fwd: "Enhanced" MD code avaible for review]
Date: Wed, 17 Mar 2004 11:54:05 -0700 [thread overview]
Message-ID: <2241002704.1079549645@aslan.btc.adaptec.com> (raw)
In-Reply-To: <20040317183756.GA23667@lst.de>
> On Wed, Mar 17, 2004 at 01:33:12PM -0500, Jeff Garzik wrote:
>> A patch to fs/partitions/check.c is also required for this
>> release to function correctly:
Hmm. I don't think Jeff wrote that.
>> http://people.freebsd.org/~gibbs/linux/SRC/md_announce_whole_device.diff
>
> Vetoed. Kernel-level autodetection code is deprecated already, don't
> even try to add functionality for it.
So do you speak for the entire community in expressing that auto-detection
will never make sense in the kernel? Are you completely unwilling to
entertain even a minor discussion on the topic for those of us that don't
understand the concerns the community has in supporting it?
> As for the actual code please post diffs instead of tarballs.
If you look at the posted code, you'll see that diffs make little
sense at this point. But I will generate diffs in addition
to the tarball with the next release later this week.
--
Justin
next prev parent reply other threads:[~2004-03-17 18:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <405899E8.8070806@pobox.com>
2004-03-17 18:37 ` [Fwd: "Enhanced" MD code avaible for review] Christoph Hellwig
2004-03-17 18:54 ` Justin T. Gibbs [this message]
2004-03-17 19:01 ` Christoph Hellwig
2004-03-17 19:05 ` Justin T. Gibbs
2004-03-17 19:09 ` Christoph Hellwig
2004-03-17 19:28 ` Jeff Garzik
2004-03-17 19:34 ` Christoph Hellwig
2004-03-17 19:41 ` Jeff Garzik
2004-03-17 19:23 ` Hendrik Visage
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=2241002704.1079549645@aslan.btc.adaptec.com \
--to=justin_gibbs@adaptec.com \
--cc=hch@lst.de \
--cc=linux-raid@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;
as well as URLs for NNTP newsgroup(s).