lkml.org 
[lkml]   [2008]   [May]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: linux-next: the purge :-)
On Thu, May 08, 2008 at 08:44:27PM -0700, Greg KH wrote:
> On Fri, May 09, 2008 at 11:16:08AM +1000, Stephen Rothwell wrote:
> > Hi Greg,
> >
> > On Thu, 8 May 2008 15:04:43 -0700 Greg KH <greg@kroah.com> wrote:
> > >
> > > 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:
> > > > >
> > > > > 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.
>
> Ok, I'll go rename them to be ".current" instead of ".next"

Now done, the sequence is:
driver-core.current
usb.current
driver-core
usb
ldp.next

I left ldp.next as that is really only for the -next tree.

If you have any problems with this, please let me know.

thanks,

greg k-h


\
 
 \ /
  Last update: 2008-05-09 06:21    [W:0.046 / U:0.116 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site