linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Darrell Michaud <dmichaud@wsi.com>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: 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: 02 Dec 2003 11:10:43 -0500	[thread overview]
Message-ID: <1070381443.5316.260.camel@atherne> (raw)
In-Reply-To: <Pine.LNX.4.44.0312021346530.13692-100000@logos.cnet>

As a user it would be very beneficial for me to have XFS support in the
official 2.4 kernel tree. XFS been stable and "2.4 integration-ready"
for a long time, and 2.4 is going to be used in certain environments for
a long time, if only because it's easier to upgrade a 2.4 kernel to a
newer 2.4 kernel than to upgrade to a 2.6 kernel. It seems like an easy
case to make.

I use other filesystems and some funky drivers as well.. and I'm always
very happy to see useful backports show up in the 2.4 tree. Thank you!



On Tue, 2003-12-02 at 10:50, Marcelo Tosatti wrote:
> On Tue, 2 Dec 2003, Russell Cattelan wrote:
> 
> > On Tue, 2003-12-02 at 05:18, Marcelo Tosatti wrote:
> > [snip] 
> > > Also I'm not completly sure if the generic changes are fine and I dont
> > > like the XFS code in general.
> > Ahh so the real truth comes out.
> > 
> > 
> > Is there a reason for your sudden dislike of the XFS code?
> 
> I always disliked the XFS code. 
> 
> > or is this just an arbitrary general dislike for unknown or unstated
> > reasons?
> 
> I dont like the style of the code. Thats a personal issue, though, and 
> shouldnt matter.
> 
> The bigger point is that XFS touches generic code and I'm not sure if that 
> can break something.
> 
> Why it matters so much for you to have XFS in 2.4 ? 
> 
-- 
Darrell Michaud <dmichaud@wsi.com>


  reply	other threads:[~2003-12-02 16:11 UTC|newest]

Thread overview: 79+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-01  6:20 XFS for 2.4 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 [this message]
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-14  1:08   ` 2.4 vs 2.6 Jan Rychter
2003-12-14  1:01     ` Roberto Sanchez
2003-12-14 11:23       ` Måns Rullgård
2003-12-14 18:09         ` Daniel Gryniewicz
2003-12-14  1:53     ` Daniel Gryniewicz
2003-12-14  2:01     ` coderman
2003-12-14 20:23       ` tabris
2003-12-14  7:05     ` Voicu Liviu
2003-12-14 16:01       ` Roberto Sanchez
2003-12-14 17:32         ` Voicu Liviu
2003-12-15  7:23           ` Harry McGregor
2003-12-15  7:51             ` Voicu Liviu
2003-12-14 11:24     ` Frederik Deweerdt
2003-12-01 21:00 ` XFS for 2.4 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
2003-12-02 17:45 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
2003-12-03 21:06     ` Marcelo Tosatti
2003-12-03 22:07     ` grundig
2003-12-03 22:48       ` bill davidsen
2003-12-02 18:34 Murthy Kambhampaty
2003-12-04  1:27 Xose Vazquez Perez
2003-12-04  2:40 ` Bernd Eckenfels

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=1070381443.5316.260.camel@atherne \
    --to=dmichaud@wsi.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=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).