From: "Đoàn Trần Công Danh" <congdanhqx@gmail.com>
To: Claus Fischer <claus.fischer@clausfischer.com>
Cc: git@vger.kernel.org
Subject: Re: Scriptable mode for git bisect
Date: Sat, 24 Sep 2022 08:44:19 +0700 [thread overview]
Message-ID: <Yy5g80OtVG4op8L1@danh.dev> (raw)
In-Reply-To: <Yy4c6/jHupgThj7j@clausfischer.com>
On 2022-09-23 22:54:03+0200, Claus Fischer <claus.fischer@clausfischer.com> wrote:
>
> Dear Git maintainers,
>
> I have looked at the manpage of git bisect but have not found
> what I need:
> I would like git bisect not just to report the 'bad' revision
> within a bunch of text but instead either stop at the first
> bad revision (the last good will then be HEAD~1) or report
> it in a scriptable way, i.e.
>
> BADHEAD=$(git bisect run --shut-up-and-report-the-bad)
>
> Have I overlooked anything?
After running "git bisect run"
You can take its revisions with:
BADHEAD=$(git rev-parse --verify refs/bisect/bad)
>
> ***
>
> The pourpose is to keep the source trees of two different
> projects that share a few files synchronous.
> My good/bad-script is a script that checks whether these
> files are similar.
> I want git to stop at the first change in source tree A
> so that I can update source tree B with the same commit
> message, then proceed to the next change in A that
> changes one of those files.
>
> Regards,
>
> Cluas
--
Danh
next prev parent reply other threads:[~2022-09-24 1:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-23 20:54 Scriptable mode for git bisect Claus Fischer
2022-09-24 1:44 ` Đoàn Trần Công Danh [this message]
2022-09-24 9:32 ` Claus Fischer
2022-09-24 9:46 ` Đoàn Trần Công Danh
2022-09-24 16:24 ` Junio C Hamano
[not found] ` <69B998A9-0E3E-45F0-8733-F2A3F11625A5@clausfischer.com>
2022-09-25 0:59 ` Đoàn Trần Công Danh
2022-09-25 12:42 ` Claus Fischer
2022-09-26 17:00 ` Junio C Hamano
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=Yy5g80OtVG4op8L1@danh.dev \
--to=congdanhqx@gmail.com \
--cc=claus.fischer@clausfischer.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.