linux-kernel - Re: is the weeks before -rc1 the time to really be working on -next?

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]

Date:	Wed, 15 Oct 2008 13:30:38 -0700
From:	Greg KH <greg@...ah.com>
To:	Geert Uytterhoeven <geert@...ux-m68k.org>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: is the weeks before -rc1 the time to really be working on
	-next?

On Wed, Oct 15, 2008 at 10:04:17PM +0200, Geert Uytterhoeven wrote:
> On Wed, 15 Oct 2008, Greg KH wrote:
> > Just wondering, I know that -next is failing right now, and is a major
> > pain to produce, but that seems to be primarily due to all of the
> > subsystems merging with Linus right now.
> > 
> > So does it even make sense to try to create a -next during the 2 weeks
> > of the major merge window?  It seems to just cause you a whole lot of
> > work, that in the end, is mostly unecessary as all of the subsystem
> > maintainers are doing the merging themselves as trees move into Linus's
> > tree?
> 
> I don't know if it's worth the effort...
> 
> However, we definitely missed linux-next during the last few weeks, seeing
> things getting into mainline that don't even survive simple compile tests.

Oh I agree, I missed it a lot the past few weeks, it's amazing how much
we already started to rely on it in such a short time.  That shows how
valuable the effort is.

Keep it up, I just don't want to see Stephen burn out during the pre-rc1
time period when it might not make as much sense to be trying to create
the tree.

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/