From: Long 76 <long76.git@mail.ru>
To: Matt Hunter <m@lfurio.us>,
git@vger.kernel.org, phillip.wood@dunelm.org.uk
Subject: Re: REBASE_HEAD still exists after success end rebase
Date: Tue, 28 Jul 2026 18:28:55 +0300 [thread overview]
Message-ID: <b3ec5eac-a177-4991-8edc-36ce5992dad2@mail.ru> (raw)
In-Reply-To: <9ee7b916-a9ce-4300-baf4-b24d0a52fe46@mail.ru>
+ phillip.wood@dunelm.org.uk
28.07.2026 18:27, Long 76 пишет:
>> I made a very short-lived effort to look into why this "bug" was
>> happening. I say "bug" in quotes, because I'm not even sure if it is
>> even problematic behavior.
>
> I think this is a bug because git create similar HEADs if you made merge
> or cherry-pick. I don't have problems with them.
>
> Plus by git rebase docs on official site flag '--show-current-patch':
> ---
> Show the current patch in an interactive rebase or when rebase is
> stopped because of conflicts. This is the equivalent of git show
> REBASE_HEAD.
> ---
> For me it means that return patch only if rebase in progress - not
> aborted/not complete/have conflicts
>
>> I solved my need at the time (detecting a rebase in progress) by
>> checking for the existence of either of the 'rebase-merge' or
>> 'rebase-apply' directories in $GIT_DIR.
>
> Thanks for advice! I don't knew it.
prev parent reply other threads:[~2026-07-28 15:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-28 8:26 REBASE_HEAD still exists after success end rebase Long 76
2026-07-28 9:39 ` Matt Hunter
2026-07-28 13:21 ` Phillip Wood
2026-07-28 15:34 ` Long 76
2026-07-28 15:27 ` Long 76
2026-07-28 15:28 ` Long 76 [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=b3ec5eac-a177-4991-8edc-36ce5992dad2@mail.ru \
--to=long76.git@mail.ru \
--cc=git@vger.kernel.org \
--cc=m@lfurio.us \
--cc=phillip.wood@dunelm.org.uk \
/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