From: Valdis.Kletnieks@vt.edu
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: "Giacomo A. Catenazzi" <cate@cateee.net>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: Linux 2.6.24
Date: Fri, 25 Jan 2008 22:19:16 -0500 [thread overview]
Message-ID: <7766.1201317556@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Sat, 26 Jan 2008 00:50:44 +0100." <479A75D4.6070607@s5r6.in-berlin.de>
[-- Attachment #1: Type: text/plain, Size: 703 bytes --]
On Sat, 26 Jan 2008 00:50:44 +0100, Stefan Richter said:
> How often is "bisectability" being broken already before merge in
> subsystem trees, and how often only in the context of the merge result?
I don't bisect git trees often - but I'd say that at least half the time
I have to bisect -mm, I'll hit a busticated bisection point and need to
move several one way or another. Fortunately, Andrew does a good job
of keeping fixes near their parents, so it's usually not *that* hard to
clean up (at least for me - but I recently realized that I had passed the
3-decade mark of breaking and fixing software). Newcomer kernel testers
are likely in for a rude awakening if they hit one of those points.
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
next prev parent reply other threads:[~2008-01-26 3:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-24 23:17 Linus Torvalds
2008-01-24 23:41 ` Linus Torvalds
2008-01-25 9:10 ` Giacomo A. Catenazzi
2008-01-25 9:58 ` Valdis.Kletnieks
2008-01-25 11:58 ` Rafael J. Wysocki
2008-01-25 12:34 ` Giacomo A. Catenazzi
2008-01-25 23:50 ` Stefan Richter
2008-01-26 0:42 ` using LKML for subsystem development (was Re: Linux 2.6.24) Stefan Richter
2008-01-26 3:28 ` Valdis.Kletnieks
2008-01-26 13:31 ` using LKML for subsystem development Stefan Richter
2008-01-27 7:37 ` Valdis.Kletnieks
2008-01-26 11:28 ` using LKML for subsystem development (was Re: Linux 2.6.24) Ingo Molnar
2008-01-26 14:07 ` using LKML for subsystem development David Miller
2008-01-26 14:45 ` Stefan Richter
2008-01-26 14:25 ` Stefan Richter
2008-02-01 9:40 ` Ingo Molnar
2008-02-01 19:53 ` Stefan Richter
2008-01-26 3:19 ` Valdis.Kletnieks [this message]
2008-01-25 11:35 ` Linux 2.6.24 Ingo Molnar
2008-01-25 10:11 ` [PATCH] linux-2.6.24/drivers/hid/hid-input.c Philipp Matthias Hahn
2008-01-25 10:30 ` Jiri Kosina
2008-02-03 12:35 ` Linux 2.6.24 Jan Engelhardt
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=7766.1201317556@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=cate@cateee.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rjw@sisk.pl \
--cc=stefanr@s5r6.in-berlin.de \
--cc=torvalds@linux-foundation.org \
/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
all inboxes | Powered by JetHome®