From: David Howells <dhowells@redhat.com>
To: James Morris <jmorris@namei.org>
Cc: dhowells@redhat.com, simo@redhat.com, zohar@linux.vnet.ibm.com,
keyrings@linux-nfs.org, linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] Keyrings patches
Date: Tue, 10 Sep 2013 10:45:59 +0100 [thread overview]
Message-ID: <10114.1378806359@warthog.procyon.org.uk> (raw)
In-Reply-To: <alpine.LRH.2.02.1309071426400.29124@tundra.namei.org>
James Morris <jmorris@namei.org> wrote:
> > > This missed the merge for 3.12. Do you want me to queue the changes up,
> > > or do you want to send a pull request again after -rc1 ?
> >
> > Can you queue them up now in your 'next' branch?
>
> Nope, new patches can't go into -next until -rc1.
I think I misunderstood your offer. When you said "to queue the changes up"
did you mean for immediate passage to Linus? If so, is it too late for that?
David
next prev parent reply other threads:[~2013-09-10 9:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-05 0:14 [GIT PULL] Keyrings patches David Howells
2013-09-06 17:10 ` James Morris
2013-09-06 17:36 ` David Howells
2013-09-07 4:26 ` James Morris
2013-09-10 9:45 ` David Howells [this message]
2013-09-11 15:41 ` James Morris
2013-09-17 13:55 ` David Howells
2013-09-18 1:50 ` Stephen Rothwell
2013-09-18 11:53 ` David Howells
2013-09-18 12:47 ` Mimi Zohar
2013-09-18 3:17 ` Mimi Zohar
2013-09-24 2:06 ` James Morris
2013-09-24 9:31 ` David Howells
-- strict thread matches above, loose matches on Subject: below --
2013-09-25 21:21 David Howells
2013-09-27 7:40 ` James Morris
2013-09-27 16:31 ` David Howells
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=10114.1378806359@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=jmorris@namei.org \
--cc=keyrings@linux-nfs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=simo@redhat.com \
--cc=zohar@linux.vnet.ibm.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