From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: git bisect with history manipulation
Date: Mon, 23 Oct 2006 17:42:25 +0200 [thread overview]
Message-ID: <ehinsa$a7n$1@sea.gmane.org> (raw)
In-Reply-To: Pine.LNX.4.64.0610230826080.3962@g5.osdl.org
Linus Torvalds wrote:
> So depending on the problem, you can try two different approaches.
[The approaches being: 1) applying patchseries before testing, and marking
the commit before applying as good or bad for bisect; 2) rebasing
(applying) the patch-series on top of current kernel, and bisecting the
series]
You can try yet another approach, namely rebase v2.6.15..v2.6.18 on top of
your patch-series applied to v2.6.15, and bisect that.
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2006-10-23 15:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <a425f86c0610230718i556537dei9a4b2a5fa8d7f003@mail.gmail.com>
2006-10-23 14:22 ` git bisect with history manipulation Kalle Pokki
2006-10-23 15:34 ` Linus Torvalds
2006-10-23 15:42 ` Jakub Narebski [this message]
2006-10-23 15:59 ` Linus Torvalds
2006-10-23 15:47 ` Sean
2006-10-23 15:47 ` Sean
2006-10-23 16:19 ` Jakub Narebski
2006-10-23 16:25 ` Sean
2006-10-23 16:25 ` Sean
2006-10-23 16:21 ` Catalin Marinas
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='ehinsa$a7n$1@sea.gmane.org' \
--to=jnareb@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.