threads / discuss / 5492

stgit bisect feature request

Subject: stgit bisect feature request

## tl;dr

3 messages between Sep 5, 2006 and Sep 6, 2006.

replies: 2people: 3as markdown or json

Torgil Svensson· Sep 5, 2006, 23:49 UTC · lore

I think i'd be nice if stgit wraps bisect and you could write $ stg bisect start $ stg bisect bad $ stg bisect good ORIG_HEAD

and after bisect checks out the files it pushes the current stack as if you had used stg pull at this point

//Torgil

Karl Hasselström· Sep 6, 2006, 08:31 UTC · re: Torgil Svensson · lore

Re: stgit bisect feature request

On 2006-09-06 01:49:15 +0200, Torgil Svensson wrote:

Show 8 quoted lines

> I think i'd be nice if stgit wraps bisect and you could write
>
> $ stg bisect start
> $ stg bisect bad
> $ stg bisect good ORIG_HEAD
>
> and after bisect checks out the files it pushes the current stack as
> if you had used stg pull at this point

Yes, this sounds very useful for bisecting when you can't test the old revisions as-is, e.g. because you have to patch for an unrelated bug, or because you need a patch to trigger the problem.

-- 
Karl Hasselström, kha@treskal.com
      www.treskal.com/kalle

Catalin Marinas· Sep 6, 2006, 08:36 UTC · re: Torgil Svensson · lore

Re: stgit bisect feature request

"Torgil Svensson" <torgil.svensson@gmail.com> wrote:

Show 7 quoted lines

> I think i'd be nice if stgit wraps bisect and you could write
> $ stg bisect start
> $ stg bisect bad
> $ stg bisect good ORIG_HEAD
>
> and after bisect checks out the files it pushes the current stack as
> if you had used stg pull at this point

It would be nice but there could be conflicts when pushing patches, especially if you do the bisect over a larger range of commits. It gets difficult if some StGIT patches rely on features not present some of the commits you are checking.

Have you tried this idea manually (or with some scripts) and found it feasible?

-- 
Catalin