git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: REBASE_HEAD still exists after success end rebase

From
L7Long 76 <long76.git@mail.ru>
Date
Jul 28, 2026, 15:28 UTC
Message-ID
<b3ec5eac-a177-4991-8edc-36ce5992dad2@mail.ru>
In-Reply-To
<9ee7b916-a9ce-4300-baf4-b24d0a52fe46@mail.ru>
+ phillip.wood@dunelm.org.uk
28.07.2026 18:27, Long 76 пишет:
Show 21 quoted lines
>> 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.
Previous: Long 76
Message 6 of 6 in “REBASE_HEAD still exists after success end rebase”
  1. Long 76Jul 28, 2026
  2. Matt HunterJul 28, 2026
  3. Phillip WoodJul 28, 2026
  4. Long 76Jul 28, 2026
  5. Long 76Jul 28, 2026
  6. Long 76Jul 28, 2026

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.