[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140620145716.GA28243@mail.hallyn.com>
Date: Fri, 20 Jun 2014 16:57:16 +0200
From: "Serge E. Hallyn" <serge@...lyn.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: "Serge E. Hallyn" <serge@...lyn.com>,
Paul Moore <paul@...l-moore.com>, linux-next@...r.kernel.org,
linux-kernel@...r.kernel.org,
James Morris <james.l.morris@...cle.com>
Subject: Re: linux-next: the selinux tree needs cleaning up
Quoting Stephen Rothwell (sfr@...b.auug.org.au):
> Hi Serge,
>
> On Fri, 20 Jun 2014 05:43:56 +0200 "Serge E. Hallyn" <serge@...lyn.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists