From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "Luis R. Rodriguez" <mcgrof@frijolero.org>,
linux-kernel@vger.kernel.org,
linux-wireless <linux-wireless@vger.kernel.org>,
Johannes Berg <johannes@sipsolutions.net>,
"John W. Linville" <linville@tuxdriver.com>
Subject: Re: Is linux-next.git bisectable?
Date: Tue, 6 Dec 2011 19:53:53 +0100 [thread overview]
Message-ID: <20111206195353.6f9a0881@stein> (raw)
In-Reply-To: <20111206113346.57b3efd85780b6ff18076e9c@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 907 bytes --]
On Dec 06 Stephen Rothwell wrote:
> On Mon, 5 Dec 2011 16:29:36 -0800 "Luis R. Rodriguez" <mcgrof@frijolero.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/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2011-12-06 18:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-06 0:29 Is linux-next.git bisectable? Luis R. Rodriguez
2011-12-06 0:33 ` Stephen Rothwell
2011-12-06 18:53 ` Stefan Richter [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20111206195353.6f9a0881@stein \
--to=stefanr@s5r6.in-berlin.de \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@frijolero.org \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).