From: Mark Goodwin <markgw@sgi.com>
To: Christoph Hellwig <hch@lst.de>
Cc: xfs@oss.sgi.com
Subject: Re: take messages
Date: Mon, 19 May 2008 10:30:32 +1000 [thread overview]
Message-ID: <4830CA28.9060805@sgi.com> (raw)
In-Reply-To: <20080518102710.GA17618@lst.de>
Christoph Hellwig wrote:
> folks, any chance to get take messages sent to the list, please?
do you mean for any checkin, or just oss pushes?
> Kust
> saw the tree is merged up to 2.6.25 (why not .26-rc, btw?) and there's
> been no take message sent to the list again..
>
Lachlan was held up with QA failures on updating the internal dev tree,
which was in turn holding up .26-rc I think.
Lachlan, what's the status with this?
Thanks
--
Mark Goodwin markgw@sgi.com
Engineering Manager for XFS and PCP Phone: +61-3-99631937
SGI Australian Software Group Cell: +61-4-18969583
-------------------------------------------------------------
next prev parent reply other threads:[~2008-05-19 0:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-18 10:27 take messages Christoph Hellwig
2008-05-19 0:30 ` Mark Goodwin [this message]
2008-05-19 6:00 ` Christoph Hellwig
2008-05-20 1:50 ` Lachlan McIlroy
2008-05-20 10:20 ` Christoph Hellwig
2008-05-20 11:39 ` Mark Goodwin
2008-05-20 19:29 ` Russell Cattelan
2008-05-20 1:44 ` Lachlan McIlroy
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=4830CA28.9060805@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