From: Christoph Hellwig <hch@infradead.org>
To: Mark Goodwin <markgw@sgi.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 0/2] Urgent queue
Date: Tue, 28 Oct 2008 06:53:21 -0400 [thread overview]
Message-ID: <20081028105321.GA30522@infradead.org> (raw)
In-Reply-To: <4906EB5B.2020004@sgi.com>
On Tue, Oct 28, 2008 at 09:37:15PM +1100, Mark Goodwin wrote:
> 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 :)
Even urgent isn't urgent enough for the first 2.6.28 series, please get
that one out ASAP, I don't want to miss it. The two patches from the
urgent queue are something I would consider for a second .28 pull,
everything else is .29 material.
But it would be highly useful if we could open up a .29 staging tree that
can be QAed and included in linux-next ASAP..
next prev parent reply other threads:[~2008-10-28 11:13 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
2008-10-28 10:53 ` Christoph Hellwig [this message]
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=20081028105321.GA30522@infradead.org \
--to=hch@infradead.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.