From: Al Viro <viro@ZenIV.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [git pull] signal.git pile 2 (of 3, probably)
Date: Fri, 1 Jun 2012 03:14:31 +0100 [thread overview]
Message-ID: <20120601021430.GG30000@ZenIV.linux.org.uk> (raw)
In-Reply-To: <CA+55aFwaOT_jfOxZkG62kU+gkpAm3Q4h39NL-no8D9FhE3httQ@mail.gmail.com>
On Thu, May 31, 2012 at 06:49:00PM -0700, Linus Torvalds wrote:
> On Thu, May 31, 2012 at 4:57 PM, Al Viro <viro@zeniv.linux.org.uk> wrote:
> >
> > There probably will be another pull request from that tree this
> > cycle - at least for helpers, to get them out of the way for per-arch
> > fixes remaining in the tree.
>
> I'm likely cutting -rc1 tomorrow, and on Saturday at the latest.
> Otherwise my travel schedule will get very inconvenient wrt -rc2.
_Ouch_...
OK, then tomorrow morning you'll have vfs.git pull request. Damn...
prev parent reply other threads:[~2012-06-01 2:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-31 23:57 [git pull] signal.git pile 2 (of 3, probably) Al Viro
2012-06-01 1:49 ` Linus Torvalds
2012-06-01 2:14 ` Al Viro [this message]
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=20120601021430.GG30000@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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