linux-kernel - Re: Is linux-next.git bisectable?

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] [day] [month] [year] [list]

Message-ID: <20111206195353.6f9a0881@stein>
Date:	Tue, 6 Dec 2011 19:53:53 +0100
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	"Luis R. Rodriguez" <mcgrof@...jolero.org>,
	linux-kernel@...r.kernel.org,
	linux-wireless <linux-wireless@...r.kernel.org>,
	Johannes Berg <johannes@...solutions.net>,
	"John W. Linville" <linville@...driver.com>
Subject: Re: Is linux-next.git bisectable?

On Dec 06 Stephen Rothwell wrote:
> On Mon, 5 Dec 2011 16:29:36 -0800 "Luis R. Rodriguez" <mcgrof@...jolero.org> wrote:
> > is the linux-next.git tree bisectable? I've noticed some trees are
> > not. For example wireless-testing.git is bisectable but only between
> > master-$(date) tags.
> 
> Within any one day, the tree is bisectable, but not really between one
> day and another.  The tree is rebuilt starting from Linus' tree each day.

The individual trees that are being submitted to be pulled into linux-next
*should* be bisectable though.  This is because only stuff is meant to be
shown to linux-next for which the question
   "Cross-tree integration testing ignored for a moment,
    if Linus had a merge window open today, would I ask him to pull this
    tree right away?"
would be answered with a firm Yes.
-- 
Stefan Richter
-=====-==-== ==-- --==-
http://arcgraph.de/sr/

Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)