From: davidsen@tmr.com (bill davidsen)
To: linux-kernel@vger.kernel.org
Subject: Re: XFS for 2.4
Date: 3 Dec 2003 20:44:15 GMT [thread overview]
Message-ID: <bqlhuv$jh2$1@gatekeeper.tmr.com> (raw)
In-Reply-To: 20031202180251.GB17045@work.bitmover.com
In article <20031202180251.GB17045@work.bitmover.com>,
Larry McVoy <lm@bitmover.com> wrote:
| On Tue, Dec 02, 2003 at 12:45:38PM -0500, Murthy Kambhampaty wrote:
| > If you can't come up with something more concrete than "I don't like your
| > coding style" and "I'm not sure your patch won't break something", it seems
| > only fair you take the XFS patches.
|
| Not your call, it's Marcelo's call. And I and he have both suggested
| that the way to get XFS in is to have someone with some clout in the file
| system area agree that it is fine. It's a perfectly reasonable request
| and the longer it goes unanswered the less likely it is that XFS will get
| integrated. The fact that $XFS_USER wants it in is $XFS_USER's problem.
| $VFS_MAINTAINER needs to say "hey, this looks good, what's the fuss about?"
| and I suspect that Marcelo would be more interested.
Linus accepted it for 2.6, does it need to be blessed by the Pope, or what?
|
| It is not, however, any more my call to make than it is your call to make.
| We're not doing Marcelo's job.
|
| It is also not unreasonable to reject a set of changes right before
| freezing 2.4. 2.4 is supposed to be dead. Add XFS and what's next?
| Who's pet feature needs to go in?
Now that is bullshit and you know it! This is not a pet feature, this
is code which has has been stable for years. There just aren't any
other candidates, all the other FS stuff went in with less testing and
have fewer users now (JFS as example). This is also not code offered
"right before a freeze" this code has been offered version by version
for two bleepin' years, has it not? There's no slippery slope, there
are no other major features which have proven long-term stability. Fell
free to name them if I'm wrong...
Marcelo admits he doesn't like the coding style, he has the right to
keep out anything he doesn't like, but let's not invent other reasons.
It's his call and he made it. It's a pity he didn't make the call
earlier and save people the effort, though.
--
bill davidsen <davidsen@tmr.com>
CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.
next prev parent reply other threads:[~2003-12-03 20:55 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-02 17:45 XFS for 2.4 Murthy Kambhampaty
2003-12-02 17:59 ` Jeff Garzik
2003-12-03 20:10 ` bill davidsen
2003-12-02 18:01 ` Marcelo Tosatti
2003-12-02 19:10 ` Tomas Szepe
2003-12-03 0:13 ` Eric Sandall
2003-12-03 20:12 ` bill davidsen
2003-12-02 18:02 ` Larry McVoy
2003-12-02 18:11 ` Christoph Hellwig
[not found] ` <20031202181146.A27567@adic.com>
2003-12-02 18:19 ` Steve Lord
2003-12-02 18:20 ` Larry McVoy
2003-12-02 18:23 ` Christoph Hellwig
2003-12-02 18:27 ` Christoph Hellwig
2003-12-02 19:12 ` Marcelo Tosatti
2003-12-02 20:10 ` Nathan Scott
2003-12-02 20:11 ` viro
2003-12-03 20:51 ` bill davidsen
2003-12-03 20:44 ` bill davidsen [this message]
2003-12-03 21:06 ` Marcelo Tosatti
2003-12-03 22:07 ` grundig
2003-12-03 22:48 ` bill davidsen
-- strict thread matches above, loose matches on Subject: below --
2003-12-04 1:27 Xose Vazquez Perez
2003-12-04 2:40 ` Bernd Eckenfels
2003-12-02 18:34 Murthy Kambhampaty
2003-12-01 6:20 Nathan Scott
2003-12-01 9:24 ` Jens Axboe
2003-12-01 9:44 ` Stefan Smietanowski
2003-12-01 9:45 ` Jens Axboe
2003-12-01 14:06 ` Marcelo Tosatti
2003-12-01 22:10 ` Nathan Scott
2003-12-01 22:20 ` Larry McVoy
2003-12-02 0:23 ` Nathan Scott
2003-12-02 11:22 ` Marcelo Tosatti
2003-12-02 18:05 ` Austin Gonyou
2003-12-02 19:55 ` Stephan von Krawczynski
2003-12-02 20:05 ` Marcelo Tosatti
2003-12-02 20:16 ` Lawrence Walton
2003-12-03 19:01 ` bill davidsen
2003-12-03 20:45 ` Willy Tarreau
2003-12-03 21:17 ` bill davidsen
2003-12-03 21:48 ` Joel Becker
2003-12-03 22:17 ` bill davidsen
2003-12-03 22:08 ` Ed Sweetman
2003-12-04 5:21 ` Willy Tarreau
2003-12-04 0:34 ` Clemens Schwaighofer
2003-12-04 5:33 ` Willy Tarreau
2003-12-04 10:13 ` Clemens Schwaighofer
2003-12-02 11:18 ` Marcelo Tosatti
2003-12-02 11:48 ` Marcelo Tosatti
2003-12-02 15:34 ` Russell Cattelan
2003-12-02 15:50 ` Marcelo Tosatti
2003-12-02 16:10 ` Darrell Michaud
2003-12-02 16:21 ` Austin Gonyou
2003-12-02 16:28 ` Jeff Garzik
2003-12-02 16:57 ` venom
2003-12-02 17:41 ` Stefan Smietanowski
2003-12-02 18:01 ` Russell Cattelan
2003-12-02 16:13 ` Jeremy Jackson
2003-12-02 0:51 ` Clemens Schwaighofer
2003-12-02 1:26 ` Marcos D. Marado Torres
2003-12-01 21:00 ` Dan Yocum
2003-12-01 21:50 ` Bryan Whitehead
2003-12-01 22:01 ` Jeffrey E. Hundstad
2003-12-01 22:13 ` Gerardo Exequiel Pozzi
2003-12-02 2:54 ` Joshua Schmidlkofer
2003-12-02 11:02 ` Maciej Soltysiak
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='bqlhuv$jh2$1@gatekeeper.tmr.com' \
--to=davidsen@tmr.com \
--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;
as well as URLs for NNTP newsgroup(s).