From: Linus Torvalds <torvalds@osdl.org>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git bisect with history manipulation
Date: Mon, 23 Oct 2006 08:59:52 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0610230855260.3962@g5.osdl.org> (raw)
In-Reply-To: <ehinsa$a7n$1@sea.gmane.org>
On Mon, 23 Oct 2006, Jakub Narebski wrote:
>
> 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.
Oooh.
Yeah, it's a great idea, but likely not practical (or even possible).
git-rebase really wants a linear set of patches to rebase, which you
definitely don't have for that big history. In fact, even if rebase did
the full history rebasing, if later history did a merge of an earlier
thing (ie if the patch-series that you're trying to rebase onto was based
on something that wasn't an "epoch tip", but that was in the middle of
intertwined history), you'd really be screwed.
Also, let's face it, rebasing isn't _that_ fast. So trying to rebase huge
swaths of code would be painful as hell, even if it was a nice linear
series.
But yes, for simpler situations, you could try to switch the problem
around like you suggest.
Linus
next prev parent reply other threads:[~2006-10-23 16:00 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
2006-10-23 15:59 ` Linus Torvalds [this message]
[not found] ` <20061023114738.f77efec3.seanlkml@sympatico.ca>
2006-10-23 15:47 ` Sean
2006-10-23 16:19 ` Jakub Narebski
[not found] ` <20061023122527.4c095580.seanlkml@sympatico.ca>
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=Pine.LNX.4.64.0610230855260.3962@g5.osdl.org \
--to=torvalds@osdl.org \
--cc=git@vger.kernel.org \
--cc=jnareb@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).