From: Catalin Marinas <catalin.marinas@arm.com>
To: Sean <seanlkml@sympatico.ca>
Cc: "Kalle Pokki" <kalle.pokki@iki.fi>, git@vger.kernel.org
Subject: Re: git bisect with history manipulation
Date: Mon, 23 Oct 2006 17:21:37 +0100 [thread overview]
Message-ID: <tnxlkn73svi.fsf@arm.com> (raw)
In-Reply-To: <BAYC1-PASMTP01856E85F8D54BE3CBF69EAE000@CEZ.ICE> (seanlkml@sympatico.ca's message of "Mon, 23 Oct 2006 11:47:38 -0400")
Sean <seanlkml@sympatico.ca> wrote:
> On Mon, 23 Oct 2006 17:22:41 +0300
> "Kalle Pokki" <kalle.pokki@iki.fi> wrote:
>
>> So is there any way to insert a few patches to an arbitrary point
>> backwards in time and start bisecting from that to the present time?
>> Or am I thinking this somehow all wrong?
[...]
> You could use the Stacked Git utility (which is a Quilt like clone
> built on top of Git) to help you along in this process. Actually,
> you may be able to do the same thing with Quilt itself, but i don't
> know i've never used it.
It's on my todo list to actually add bisect support to StGIT (someone
suggested it on the mailing list) but I can't give any estimates about
when this would be done. The idea is that it will only bisect the base
and push the patches on top of the new tree (at a first though, it
doesn't look difficult at all).
Otherwise, use StGIT to manage the patches and the following sequence
for bisecting:
$ git bisect start
$ stg init
$ stg pick <patch@branch>
$ stg pick <patch@branch>
$ ...
$ stg pop -a
$ git bisect good v2.6.x
$ git bisect bad
$ stg push -a
$ ... test ...
$ stg pop -a
$ git bisect good|bad
$ stg push -a
$ ...
--
Catalin
prev parent reply other threads:[~2006-10-23 16:22 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
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 [this message]
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=tnxlkn73svi.fsf@arm.com \
--to=catalin.marinas@arm.com \
--cc=catalin.marinas@gmail.com \
--cc=git@vger.kernel.org \
--cc=kalle.pokki@iki.fi \
--cc=seanlkml@sympatico.ca \
/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.