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

Re: [PATCH] rebase: mention --abort alongside --continue

From
PWPhillip Wood <phillip.wood123@gmail.com>
Date
Jul 18, 2026, 09:25 UTC
Message-ID
<9a0b542c-8984-4d73-8e24-00adf6dcd427@gmail.com>
In-Reply-To
<CAHwyqnVwDsdvvg6a2BtAYw+hYRdgKvRXwHE+uzAZjherfu5B=Q@mail.gmail.com>
On 18/07/2026 09:05, Harald Nordgren wrote:
Show 15 quoted lines
>> I wonder if the workflow that benefits from this "if exec fails,
>> give up and forget the whole thing" behavior is actually quite
>> different from what we consider the "normal" use of the command?
>> Perhaps the user is not interested in "rebasing" the history at
>> all, but is instead running a check on each and every commit.
>> That is, a more expensive version of:
>>
>>          for commit in $(git rev-list bottom..top)
>>          do
>>                  git reset --hard "$commit" &&
>>                  do the exec command || break
>>          done
>>
>> that just happens to be shorter to type?
>> Sure, that's exactly right.

I think I must be missing something; I had assumed that someone running a check on each commit wanted to ensure it passed, and, if not, they would want to fix the problem that caused the check to fail. In that case I would expect that they would want to amend the failing commit, rather than abort the rebase. What's the scenario where one wants to check a bunch of commits but not fix the ones that fail?

Thanks
Phillip
Previous: Harald NordgrenNext: Junio C Hamano
Message 13 of 14 in “rebase: mention --abort alongside --continue”
  1. rebase: mention --abort alongside --continueHarald Nordgren via GitGitGadget, Jun 15, 2026
  2. Phillip WoodJun 16, 2026
  3. Junio C HamanoJun 16, 2026
  4. Harald NordgrenJun 17, 2026
  5. Phillip WoodJun 17, 2026
  6. Junio C HamanoJun 17, 2026
  7. Harald NordgrenJun 18, 2026
  8. Junio C HamanoJun 19, 2026
  9. Harald NordgrenJul 16, 2026
  10. Phillip WoodJul 16, 2026
  11. Junio C HamanoJul 16, 2026
  12. Harald NordgrenJul 18, 2026
  13. Phillip WoodJul 18, 2026
  14. Junio C HamanoJul 20, 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.