linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Murthy Kambhampaty <murthy.kambhampaty@goeci.com>
Cc: "'Marcelo Tosatti'" <marcelo.tosatti@cyclades.com>,
	Russell Cattelan <cattelan@xfs.org>,
	Nathan Scott <nathans@sgi.com>,
	linux-kernel@vger.kernel.org, linux-xfs@oss.sgi.com,
	Andrew Morton <akpm@osdl.org>
Subject: Re: XFS for 2.4
Date: Tue, 2 Dec 2003 12:59:57 -0500	[thread overview]
Message-ID: <20031202175957.GA1990@gtf.org> (raw)
In-Reply-To: <2D92FEBFD3BE1346A6C397223A8DD3FC0924C8@THOR.goeci.com>

On Tue, Dec 02, 2003 at 12:45:38PM -0500, Murthy Kambhampaty wrote:
> i) Would the linux 2.4 kernel maintainer please stop trolling the XFS
> mailing list.

Ok, we'll avoid discussing a major point in XFS's life -- potentially
being merged into 2.4 -- on XFS list.  Makes sense.


> iii) The 2.4 series kernel is the here and now, regardless of how near we
> all hope/project the 2.6 kernel to be (has Andrew Morton even taken it over
> from Linus?). Pushing 2.6 on users, and unjustifiably blocking the adoption
> of advanced features into the current linux kernel is pretty absurd. XFS has

This is bogus logic.

Nobody is forcing 2.6 on anyone.  People who wish to use XFS in 2.4
_can do so today_...  without any merging from Marcelo.

Merging is nothing more than moving a patch from one place to another.


> 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.

This is bogus logic.

It's _very_ wise to hold off on a patch if
(a) the code is difficult to read, and therefore difficult to review and
    fix (read: style)
(b) the maintainer is not assured of patch reliability (read: "I'm not
    sure the patch won't break things")

Both (a) and (b) are vaild concerns for long term maintenance costs.

Particularly (b).  If Marcelo is not assured of patch reliability, then
he absolutely --should not-- merge XFS into 2.4.  That's just the way
the system works.  And it's a good system.

	Jeff




  reply	other threads:[~2003-12-02 18:03 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 [this message]
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
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=20031202175957.GA1990@gtf.org \
    --to=jgarzik@pobox.com \
    --cc=akpm@osdl.org \
    --cc=cattelan@xfs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@oss.sgi.com \
    --cc=marcelo.tosatti@cyclades.com \
    --cc=murthy.kambhampaty@goeci.com \
    --cc=nathans@sgi.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;
as well as URLs for NNTP newsgroup(s).