From: David Chinner <dgc@sgi.com>
To: Mark Goodwin <markgw@sgi.com>
Cc: Christoph Hellwig <hch@lst.de>, xfs@oss.sgi.com
Subject: Re: state of the cvs tree
Date: Thu, 13 Sep 2007 10:10:25 +1000 [thread overview]
Message-ID: <20070913001025.GR995458@sgi.com> (raw)
In-Reply-To: <46E870AB.30906@sgi.com>
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.
Let's plan this a little better than "ASAP". We've already got a
full queue for .24 - I'm uncomfortable with pushing anything more
given the nature of the changes we've made in this cycle and we
really want some testing time on that code before the .24 merge
window opens. Given that we are at .23-rc6 already, it won't be long
before .24-rc1 merge window is open, so lets stop pushing large
changes into the tree until after the .24-rc1 merge is done.
IOWs, I consider stuff like Eric's spin lock clean to be .25 material
at this point, not .24, and we should only be taking bug fixes and small,
contained features (e.g. fallocate support) for .24. Everything else
can wait until .25....
Thoughts?
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
next prev parent reply other threads:[~2007-09-13 0:10 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 [this message]
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
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=20070913001025.GR995458@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