From: Timothy Shimmin <tes@sgi.com>
To: markgw@sgi.com, Christoph Hellwig <hch@lst.de>
Cc: xfs@oss.sgi.com
Subject: Re: state of the cvs tree
Date: Thu, 13 Sep 2007 11:05:20 +1000 [thread overview]
Message-ID: <46E88CD0.2050309@sgi.com> (raw)
In-Reply-To: <46E870AB.30906@sgi.com>
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?
>
No I don't :-) I did have some followup dmapi fixes but they got added
yesterday.
The sgi ptools 2.6.x-xfs tree seems just fine for me, is building and
does have the 23-rc4 (only rc4 b/c only had kdb for that at the time) AFAICS.
I guess there must be something wrong then with the cvs sync.
It must be sync'ing the embedded xfs-linux tree okay but not
the 2.6.x-xfs kernel tree.
I'll see what I can find out.
BTW, sorry for not mentioning the update on oss. I will do that
next time.
--Tim
next prev parent reply other threads:[~2007-09-13 1: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
2007-09-13 0:10 ` David Chinner
2007-09-13 0:51 ` Lachlan McIlroy
2007-09-13 1:05 ` Timothy Shimmin [this message]
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=46E88CD0.2050309@sgi.com \
--to=tes@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