public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: David Chinner <dgc@sgi.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Mark Goodwin <markgw@sgi.com>, xfs@oss.sgi.com
Subject: Re: state of the cvs tree
Date: Fri, 14 Sep 2007 09:48:29 +1000	[thread overview]
Message-ID: <20070913234829.GW734179@sgi.com> (raw)
In-Reply-To: <20070913104000.GB3351@lst.de>

On Thu, Sep 13, 2007 at 12:40:00PM +0200, Christoph Hellwig wrote:
> On Thu, Sep 13, 2007 at 09:05:15AM +1000, Mark Goodwin wrote:
> > 
> > 
> > Christoph Hellwig wrote:
> > >looks like the cvs tree is broken currently - fs/xfs/ is merged up to
> > >2.6.23-rc, but everything else is still at 2.6.22-rc state leading to
> > >various compile failures.
> > 
> > I think Tim is in the middle of the .23 update and still has some more
> > to push in. Tim?
> > 
> > What else do you (or anyone for that matter) have in the pipeline for XFS?
> > Whilst we're taking huge patches and cleanups, let's get them all in asap.
> 
> I have a long pipeline waiting, but as Dave said most of that really
> shouldn't go into 2.6.24.
> 
> There's one patch from me that I sent a long time ago that's a trivial
> cleanup and should probably go into 2.6.24 still, that's
> 
> 	"[PATCH] kill unused IOMAP_EOF flag"

Ah, that's still sitting in my tree from a past life. It fell through
the cracks, I think. It should go in to .24

> One thing that is in my alreayd submitted queue that should go into CVS
> ASAP after a small review is:
> 
> 	"[PATCH] kill probe_* sysctl leftovers"

*nod*. yeah, that's pretty trivial so should go as well. 

> this is stuff that never was in mainline, so putting it in seems fine.
> 
> Then I have a patch from Eric sitting in the front of my queue,
> 
> 	"[PATCH V2] refactor xfs_mountfs for clarity & stack savings"
> 
> which might be a little too big for 2.6.24, but should at least go into
> CVS ASAP.  I think Eric would be really happy to see it in 2.6.24 aswell
> because that means FC8 could actually mount xfs out of the box without
> running out of stack or something.

Yeah, that's been floating about for a bit and has been tested in
FC8 so seems like a no-brainer for .24.

Cheers,

Dave.
-- 
Dave Chinner
Principal Engineer
SGI Australian Software Group

  parent reply	other threads:[~2007-09-13 23:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-12 12:19 state of the cvs tree Christoph Hellwig
2007-09-12 23:05 ` Mark Goodwin
2007-09-13  0:10   ` David Chinner
2007-09-13  0:51     ` Lachlan McIlroy
2007-09-13  1:05   ` Timothy Shimmin
2007-09-13 10:40   ` Christoph Hellwig
2007-09-13 10:41     ` Christoph Hellwig
2007-09-13 14:50     ` Eric Sandeen
2007-09-13 23:48     ` David Chinner [this message]
2007-09-14  2:54       ` Eric Sandeen
2007-09-13  1:41 ` Timothy Shimmin
2007-09-13  2:01   ` Timothy Shimmin
2007-09-13 10:36   ` Christoph Hellwig

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=20070913234829.GW734179@sgi.com \
    --to=dgc@sgi.com \
    --cc=hch@lst.de \
    --cc=markgw@sgi.com \
    --cc=xfs@oss.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