Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Phillip Wood <phillip.wood123@gmail.com>
Cc: Hugo Sales <hugo@hsal.es>,  git@vger.kernel.org
Subject: Re: [PATCH 0/1] rebase: add --[no-]edit to --continue
Date: Wed, 22 Jul 2026 08:36:03 -0700	[thread overview]
Message-ID: <xmqqse5brq8s.fsf@gitster.g> (raw)
In-Reply-To: <db7edc66-9b2a-47bc-98db-87d01885cef0@gmail.com> (Phillip Wood's message of "Wed, 22 Jul 2026 14:39:32 +0100")

Phillip Wood <phillip.wood123@gmail.com> writes:

> 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.


      reply	other threads:[~2026-07-22 15:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-21 14:04 [PATCH 0/1] rebase: add --[no-]edit to --continue Hugo Sales
2026-07-21 14:04 ` [PATCH 1/1] " Hugo Sales
2026-07-21 18:04 ` [PATCH 0/1] " Junio C Hamano
2026-07-22 13:39   ` Phillip Wood
2026-07-22 15:36     ` Junio C Hamano [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=xmqqse5brq8s.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=hugo@hsal.es \
    --cc=phillip.wood123@gmail.com \
    /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