From: Claus Fischer <claus.fischer@clausfischer.com>
To: "Đoàn Trần Công Danh" <congdanhqx@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Scriptable mode for git bisect
Date: Sat, 24 Sep 2022 11:32:52 +0200 [thread overview]
Message-ID: <E10623C2-FF73-4E5B-AD28-C255B02F3B0F@clausfischer.com> (raw)
In-Reply-To: <Yy5g80OtVG4op8L1@danh.dev>
I tried that but it turns out it does not always stop at the bad revision.
Claus
> On 24.09.2022, at 03:44, Đoàn Trần Công Danh <congdanhqx@gmail.com> wrote:
>
> 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 9:33 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
2022-09-24 9:32 ` Claus Fischer [this message]
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=E10623C2-FF73-4E5B-AD28-C255B02F3B0F@clausfischer.com \
--to=claus.fischer@clausfischer.com \
--cc=congdanhqx@gmail.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 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).