public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Adrian Bunk <bunk@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org,
	"John W. Linville" <linville@tuxdriver.com>,
	Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Sam Ravnborg <sam@ravnborg.org>
Subject: Re: linux-next: the purge :-)
Date: Thu, 8 May 2008 15:04:43 -0700	[thread overview]
Message-ID: <20080508220443.GE7705@kroah.com> (raw)
In-Reply-To: <20080508062715.GE14951@cs181133002.pp.htv.fi>

On Thu, May 08, 2008 at 09:27:15AM +0300, Adrian Bunk wrote:
> On Wed, May 07, 2008 at 09:27:53PM -0700, Greg KH wrote:
> > On Thu, May 08, 2008 at 11:21:30AM +1000, Stephen Rothwell wrote:
> > > Greg, you might consider setting up a subset (currently probably
> > > empty) of the ldp tree for drivers that are readier for integration.
> > 
> > Ok, fair enough, I totally understand.
> > 
> > I've now moved my trees around a bit, and would like it if you could
> > include the following, in this order (the # NEXT_BASE variable is set in
> > them to make sure things get ordered properly.)
> > 	driver-core.next
> > 	usb.next
> > 	driver-core
> > 	usb
> > 	ldp.next
> > 
> > The ".next" trees are what is going to Linus before the next major
> > release happens (bugfixes and new device ids at this point in time for
> > example.)  The other trees are what is going to go to Linus after the
> > next major kernel is out.
> >...
> 
> So the "next" in your .next has the opposite meaning of the one in 
> linux-next?

It does?  I was following the convention that people used for their git
tree branch names I thought.

> Can you name it .fixes instead to make it clearer?

I can name it anything that Stephen wants me to, I'll defer to him as he
is the only one that will ever really see this.

thanks,

greg k-h

  reply	other threads:[~2008-05-08 22:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-08  1:21 linux-next: the purge :-) Stephen Rothwell
2008-05-08  1:56 ` John W. Linville
2008-05-08  4:33   ` Stephen Rothwell
2008-05-08  4:27 ` Greg KH
2008-05-08  6:27   ` Adrian Bunk
2008-05-08 22:04     ` Greg KH [this message]
2008-05-09  1:16       ` Stephen Rothwell
2008-05-09  3:44         ` Greg KH
2008-05-09  4:18           ` Greg KH
2008-05-09  6:10             ` Stephen Rothwell
2008-05-08  9:55 ` Thomas Gleixner
2008-05-08 10:46   ` Stephen Rothwell

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=20080508220443.GE7705@kroah.com \
    --to=greg@kroah.com \
    --cc=akpm@linux-foundation.org \
    --cc=bunk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=mingo@elte.hu \
    --cc=sam@ravnborg.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox