linux-kernel - Re: linux-next: the purge :-)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080508220443.GE7705@kroah.com>
Date:	Thu, 8 May 2008 15:04:43 -0700
From:	Greg KH <greg@...ah.com>
To:	Adrian Bunk <bunk@...nel.org>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org,
	"John W. Linville" <linville@...driver.com>,
	Ingo Molnar <mingo@...e.hu>,
	LKML <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Sam Ravnborg <sam@...nborg.org>
Subject: Re: linux-next: the purge :-)

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
--
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/