From: Catalin Marinas <catalin.marinas@arm.com>
To: "Torgil Svensson" <torgil.svensson@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: stgit bisect feature request
Date: Wed, 06 Sep 2006 09:36:20 +0100 [thread overview]
Message-ID: <tnxfyf5qtmj.fsf@arm.com> (raw)
In-Reply-To: <e7bda7770609051649j56a92085i8d8a73ab12004c43@mail.gmail.com> (Torgil Svensson's message of "Wed, 6 Sep 2006 01:49:15 +0200")
"Torgil Svensson" <torgil.svensson@gmail.com> wrote:
> 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
prev parent reply other threads:[~2006-09-06 8:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-05 23:49 stgit bisect feature request Torgil Svensson
2006-09-06 8:31 ` Karl Hasselström
2006-09-06 8:36 ` 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=tnxfyf5qtmj.fsf@arm.com \
--to=catalin.marinas@arm.com \
--cc=catalin.marinas@gmail.com \
--cc=git@vger.kernel.org \
--cc=torgil.svensson@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).