public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Goodwin <markgw@sgi.com>
To: Christoph Hellwig <hch@lst.de>
Cc: xfs@oss.sgi.com
Subject: Re: state of the cvs tree
Date: Thu, 13 Sep 2007 09:05:15 +1000	[thread overview]
Message-ID: <46E870AB.30906@sgi.com> (raw)
In-Reply-To: <20070912121938.GA16870@lst.de>



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.

Thanks

-- 

  Mark Goodwin                                  markgw@sgi.com
  Engineering Manager for XFS and PCP    Phone: +61-3-99631937
  SGI Australian Software Group           Cell: +61-4-18969583
-------------------------------------------------------------

  reply	other threads:[~2007-09-12 23:05 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 [this message]
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
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=46E870AB.30906@sgi.com \
    --to=markgw@sgi.com \
    --cc=hch@lst.de \
    --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