From: Andreas Schwab <schwab@linux-m68k.org>
To: walt <w41ter@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Bisecting through the middle of a big merge?
Date: Sat, 28 Jan 2012 09:55:28 +0100 [thread overview]
Message-ID: <m239b0fbpb.fsf@igel.home> (raw)
In-Reply-To: <jfve09$ih5$1@dough.gmane.org> (walt's message of "Fri, 27 Jan 2012 16:03:20 -0800")
walt <w41ter@gmail.com> writes:
> There are many individual commits from Tejun Heo et al included
> in that one big commit from Linus. Unfortunately for me, some of
> those commits cause other problems that I'm not trying to bisect;
> other problems that evidently get fixed by other commits in the
> same big merge.
>
> So I do 'git bisect skip' six or eight times until the 'false' bug
> goes away, and that leaves me at the end of the bisect without finding
> the individual commit that's causing my 'real' bug.
>
> How do you experts handle this kind of problem?
If you can identify the commit that fixes the unrelated problem you can
try to cherry-pick it during the bisect.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2012-01-28 17:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-28 0:03 Bisecting through the middle of a big merge? walt
2012-01-28 8:55 ` Andreas Schwab [this message]
2012-01-28 18:15 ` walt
2012-01-28 19:47 ` Andreas Schwab
2012-01-28 22:18 ` walt
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=m239b0fbpb.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=git@vger.kernel.org \
--cc=w41ter@gmail.com \
/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).