From: Junio C Hamano <gitster@pobox.com>
To: "Øystein Walle" <oystwa@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] rebase: write script before initializing state
Date: Tue, 08 Jul 2025 17:14:13 -0700 [thread overview]
Message-ID: <xmqqfrf6qkyy.fsf@gitster.g> (raw)
In-Reply-To: <20250609221055.136074-1-oystwa@gmail.com> ("Øystein Walle"'s message of "Tue, 10 Jun 2025 00:10:55 +0200")
Øystein Walle <oystwa@gmail.com> writes:
> If rebase.instructionFormat is invalid the repository is left in a
> strange state when the interactive rebase fails. `git status` outputs
> boths the same as it would in the normal case *and* something related to
> interactive rebase:
>
> $ git -c rebase.instructionFormat=blah rebase -i
> fatal: invalid --pretty format: blah
> $ git status
> On branch master
> Your branch is ahead of 'upstream/master' by 1 commit.
> (use "git push" to publish your local commits)
>
> git-rebase-todo is missing.
> No commands done.
> No commands remaining.
> You are currently editing a commit while rebasing branch 'master' on '8db3019401'.
> (use "git commit --amend" to amend the current commit)
> (use "git rebase --continue" once you are satisfied with your changes)
>
> By attempting to write the rebase script before initializing the state
> this potential scenario is avoided.
> ---
> The diff looks perhaps more messy than required. The only required
> change is the filling in of make_script_args and the call to
> sequencer_make_script() above the call to init_basic_state(). But then
> the `if (ret)` looks out of place, and moving that up means adding `goto
> cleanup` which means the code that was previously the else case can be
> dedented.
>
> get_commit_format() calls die() in this case, so cleaning up the
> sequencer state isn't an option. Maybe it shouldn't call die in the
> first place, but that looks to be much larger change.
The patch has been stalled for a few weeks since Phillip's review
comments. What's the status of this? Will we see a response and/or
an updated patch sometime soon?
Thanks.
next prev parent reply other threads:[~2025-07-09 0:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-09 22:10 [PATCH] rebase: write script before initializing state Øystein Walle
2025-06-09 23:03 ` Junio C Hamano
2025-06-10 10:13 ` Phillip Wood
2025-07-09 0:14 ` Junio C Hamano [this message]
2025-07-11 20:36 ` [PATCH v2] " Øystein Walle
2025-07-11 21:25 ` Junio C Hamano
2025-07-24 14:22 ` Phillip Wood
2025-07-23 21:34 ` Junio C Hamano
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=xmqqfrf6qkyy.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=oystwa@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.