linux-kernel - Re: linux-next: current pending merge fix patches

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: <20100301091916.GA30098@elte.hu>
Date:	Mon, 1 Mar 2010 10:19:16 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	Linus <torvalds@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>, linux-next@...r.kernel.org,
	Len Brown <lenb@...nel.org>, Dave Jones <davej@...hat.com>,
	Jean Delvare <khali@...ux-fr.org>, Greg KH <greg@...ah.com>,
	"J. Bruce Fields" <bfields@...ldses.org>,
	Trond Myklebust <trond.myklebust@....uio.no>,
	Sage Weil <sage@...dream.net>,
	Pekka Enberg <penberg@...helsinki.fi>,
	Christoph Lameter <cl@...ux-foundation.org>,
	Tejun Heo <tj@...nel.org>,
	Rusty Russell <rusty@...tcorp.com.au>,
	Al Viro <viro@...IV.linux.org.uk>,
	J??rn Engel <joern@...fs.org>
Subject: Re: linux-next: current pending merge fix patches


* Ingo Molnar <mingo@...e.hu> wrote:

> 
> * Ingo Molnar <mingo@...e.hu> wrote:
> 
> > So i'd argue to not backmerge during the merge window (and i have stopped 
> > doing that myself a few cycles ago, and it clearly helped things) - but in 
> > any case it's certainly no big deal and up to Linus i guess.
> 
> What i do instead is that once Linus pulls from me i pull back immediately 
> to test, and if it's fine i base further subsystem patches on that and test 
> the heck out of the combination from that point on.

A sidenote: this is only advisable if the testing in the subsystem tree is 
strong, if there were many changes with interactions and if Linus's tree is 
still in its stable phase (like now).

For slower-pace subsystems it's often good to be even more conservative with 
backmerges: to wait until -rc1 with any backmerges and to to generally not 
backmerge non-rc-release versions of Linus's tree.

That way the development commits and the followup fix commits stay in one 
linear branch of history, with no backmerge inbetween, easily bisectable and 
testable on a stable base all the way.

Thanks,

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