public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: James Morris <jmorris@namei.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	David Howells <dhowells@redhat.com>,
	Al Viro <viro@ftp.linux.org.uk>,
	linux-kernel@vger.kernel.org
Subject: Re: [GIT] New Credentials API (preliminary patches for 2.6.27) [updated]
Date: Wed, 30 Jul 2008 08:55:40 +1000 (EST)	[thread overview]
Message-ID: <Xine.LNX.4.64.0807300841430.10277@us.intercode.com.au> (raw)
In-Reply-To: <Xine.LNX.4.64.0807291043190.18657@us.intercode.com.au>

On Tue, 29 Jul 2008, James Morris wrote:

> On Sat, 26 Jul 2008, James Morris wrote:
> 
> > A new credentials framework has been developed by David Howells.  The code 
> > has been through several iterations of posting and review, and is 
> > considered by various folk to be ready to merge into linux-next.
> 
> These patches have been updated by David to resolve conflicts in current 
> git, re-tested, and may be pulled cleanly per below.
> 

Linus,

Would you be able to provide some guidance on a strategy for getting these 
credentials changes merged?  I gather they've missed the boat for 2.6.27 
(although, they are now essentially reduced to API-level changes, and not 
as scary as they look).

Stephen is not keen on taking them in linux-next, as there'll be constant 
merge conflicts, and I'm not sure whether there'd be value in dropping 
them in at the end each day.

There seems to be two options at this stage:

1. Drop them into the front of linux-next and ask developers to maintain
trees against that.  Perhaps this is how API changes in general could 
happen?

2. Maintain them separately until the very start of the next merge window 
and get them in up front when it opens.

Thoughts?



- James
-- 
James Morris
<jmorris@namei.org>

      reply	other threads:[~2008-07-29 22:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-25 20:06 [GIT] New Credentials API (preliminary patches for 2.6.27) James Morris
2008-07-29  0:48 ` [GIT] New Credentials API (preliminary patches for 2.6.27) [updated] James Morris
2008-07-29 22:55   ` James Morris [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=Xine.LNX.4.64.0807300841430.10277@us.intercode.com.au \
    --to=jmorris@namei.org \
    --cc=akpm@linux-foundation.org \
    --cc=dhowells@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=torvalds@linux-foundation.org \
    --cc=viro@ftp.linux.org.uk \
    /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