From: "Arkadiusz Miśkiewicz" <arekm@maven.pl>
To: git@vger.kernel.org
Subject: is smarter bisect possible?
Date: Fri, 25 Sep 2009 11:37:06 +0200 [thread overview]
Message-ID: <h9hrv3$cao$1@ger.gmane.org> (raw)
Hi,
I have such problem. Linus kernel tree merged some feature
(94e0fb086fc5663c38bbc0fe86d698be8314f82f) that was developed in .31rc9 era.
Current Linus kernel tree with that feature merged shows some regression.
Tree just before that merge doesn't show regression.
Now if I start to bisect just that feature (good
b7f21bb2e23b4fec16b448a34889f467465be659, bad
94e0fb086fc5663c38bbc0fe86d698be8314f82f) then git gets me whole tree back
to .31rc9 era which... doesn't show any problems.
This means that only combined current Linus tree and that feature shows a
problem.
Is it possible to make git bisect test current tree + parts of that merge
instead going back to .31rc9 era with the whole tree?
--
Arkadiusz Miśkiewicz PLD/Linux Team
arekm / maven.pl http://ftp.pld-linux.org/
next reply other threads:[~2009-09-25 7:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-25 9:37 Arkadiusz Miśkiewicz [this message]
2009-09-25 7:59 ` is smarter bisect possible? Johannes Sixt
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='h9hrv3$cao$1@ger.gmane.org' \
--to=arekm@maven.pl \
--cc=git@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).