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

Re: [PATCH 0/1] rebase: add --[no-]edit to --continue

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 22, 2026, 15:36 UTC
Message-ID
<xmqqse5brq8s.fsf@gitster.g>
In-Reply-To
<db7edc66-9b2a-47bc-98db-87d01885cef0@gmail.com>
Phillip Wood <phillip.wood123@gmail.com> writes:
Show 15 quoted lines
> On 21/07/2026 19:04, Junio C Hamano wrote:
>> Hugo Sales <hugo@hsal.es> writes:
>> 
>>> When a rebase stops for conflicts and the user runs `git rebase --continue`, the
>>> merge backend opens $EDITOR so the commit message can be revised. That is often
>>> useful, but not always: sometimes the user only wants to keep the message that
>>> is already there.
>>>
>>> This series adds:
>>>
>>> - `git rebase --continue --no-edit` to commit without opening an editor
>> 
>> Meh. "GIT_SEQUENCE_EDITOR=: git rebase --continue" is your friend ;-)
>
> Do you mean "GIT_EDITOR=:"? The sequence editor is only relevant for 

Oh, absolutely. I made a last minute change s/_EDITOR/SEQUENCE_&/ before sending it out, without realizing that I made a totally unnecessary change X-<.

Thanks for spotting.
> editing the todo list.
Previous: Phillip Wood
Message 5 of 5 in “rebase: add --[no-]edit to --continue”
  1. 0/1 rebase: add --[no-]edit to --continueHugo Sales, Jul 21, 2026
  2. 1/1 rebase: add --[no-]edit to --continueHugo Sales, Jul 21, 2026
  3. Junio C HamanoJul 21, 2026
  4. Phillip WoodJul 22, 2026
  5. Junio C HamanoJul 22, 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.