All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Serge E. Hallyn" <serge@hallyn.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "Serge E. Hallyn" <serge@hallyn.com>,
	Paul Moore <paul@paul-moore.com>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	James Morris <james.l.morris@oracle.com>
Subject: Re: linux-next: the selinux tree needs cleaning up
Date: Fri, 20 Jun 2014 16:57:16 +0200	[thread overview]
Message-ID: <20140620145716.GA28243@mail.hallyn.com> (raw)
In-Reply-To: <20140620135912.48ee1dff@canb.auug.org.au>

Quoting Stephen Rothwell (sfr@canb.auug.org.au):
> Hi Serge,
> 
> On Fri, 20 Jun 2014 05:43:56 +0200 "Serge E. Hallyn" <serge@hallyn.com> wrote:
> >
> > The duplicates were the result of several misunderstandings and general
> > naivity all on my part.  I'm actually still not clear on what usually
> > happens with the selinux tree - it feeds into linux-next, then gets
> > 'pull'ed by James into security-next for a pull request?  Do you usually
> > send a request to James when ready, he pulls, then he sends pull request
> > to Linus?  (Or am I wrong, and you usually send your own requests to
> > Linus?)
> 
> If "you" is Paul, then I am pretty sure he asks James to pull and then
> James in turn asks Linus to pull.
> 
> If "you" is me, then no :-)

Thanks :)

-serge

  reply	other threads:[~2014-06-20 14:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-17 22:40 linux-next: the selinux tree needs cleaning up Stephen Rothwell
2014-06-18 18:26 ` Paul Moore
2014-06-19 15:08   ` Stephen Rothwell
2014-06-19 19:47     ` Paul Moore
2014-06-19 22:59       ` Stephen Rothwell
2014-06-20  3:43         ` Serge E. Hallyn
2014-06-20  3:59           ` Stephen Rothwell
2014-06-20 14:57             ` Serge E. Hallyn [this message]
2014-06-20 16:06         ` Paul Moore
2014-06-24 18:03           ` Paul Moore
2014-06-24 23:59             ` Stephen Rothwell
2014-06-25 10:51               ` James Morris
2014-06-25 22:12                 ` Stephen Rothwell
2014-06-27  2:41                   ` James Morris
2014-06-25 14:14               ` Paul Moore

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=20140620145716.GA28243@mail.hallyn.com \
    --to=serge@hallyn.com \
    --cc=james.l.morris@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=paul@paul-moore.com \
    --cc=sfr@canb.auug.org.au \
    /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.