From: Mark Goodwin <markgw@sgi.com>
To: Christoph Hellwig <hch@infradead.org>, xfs@oss.sgi.com
Subject: Re: [PATCH 0/2] Urgent queue
Date: Tue, 28 Oct 2008 21:37:15 +1100 [thread overview]
Message-ID: <4906EB5B.2020004@sgi.com> (raw)
In-Reply-To: <20081028064150.GS4985@disturbed>
Dave Chinner wrote:
> On Mon, Oct 27, 2008 at 09:30:10AM -0400, Christoph Hellwig wrote:
>> Two patches that are small bugfixes / features that are what I consider the
>> immediately merge queue.
>
> The entire set of 30 patches has passed XFSQA on my test box....
individually (by series) or only after all 30? Bisectability is important,
as Christoph alluded to in another thread. Is the intention to try and take
this lot for 28-rc3? I think Lachlan is now very close to a pull req for
.28, depending on his testing for the memleak and deadlock fixes - time
is now getting pretty short :)
Cheers
-- Mark
next prev parent reply other threads:[~2008-10-28 11:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-27 13:30 [PATCH 0/2] Urgent queue Christoph Hellwig
2008-10-28 6:41 ` Dave Chinner
2008-10-28 10:37 ` Mark Goodwin [this message]
2008-10-28 10:53 ` Christoph Hellwig
2008-11-03 0:43 ` Dave Chinner
-- strict thread matches above, loose matches on Subject: below --
2008-10-26 20:34 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=4906EB5B.2020004@sgi.com \
--to=markgw@sgi.com \
--cc=hch@infradead.org \
--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