450efe2d53
If the user runs git log while rewording a commit it is confusing if
sometimes we're amending the commit that's being reworded and at other
times we're creating a new commit depending on whether we could
fast-forward or not[1]. Fix this inconsistency by always committing the
picked commit and then running 'git commit --amend' to do the reword.
The first commit is performed by the sequencer without forking git
commit and does not impact on the speed of rebase. In a test rewording
100 commits with
GIT_EDITOR=true GIT_SEQUENCE_EDITOR='sed -i s/pick/reword/' \
../bin-wrappers/git rebase -i --root
and taking the best of three runs the current master took
957ms and with this patch it took 961ms.
This change fixes rewording the new root commit when rearranging commits
with --root.
Note that the new code no longer updates CHERRY_PICK_HEAD after creating
a root commit - I'm not sure why the old code was that creating that ref
after a successful commit, everywhere else it is removed after a
successful commit.
[1] https://public-inbox.org/git/xmqqlfvu4be3.fsf@gitster-ct.c.googlers.com/T/#m133009cb91cf0917bcf667300f061178be56680a
Reported-by: SZEDER Gábor <szeder.dev@gmail.com>
Signed-off-by: Phillip Wood <phillip.wood@dunelm.org.uk>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
19 lines
570 B
Plaintext
19 lines
570 B
Plaintext
message [edit rebase-13]
|
|
message (no editor) [edit rebase-13]
|
|
message [squash rebase-12]
|
|
message (no editor) [squash rebase-11]
|
|
default [edit rebase-10]
|
|
message (no editor) [edit rebase-10]
|
|
message [fixup rebase-9]
|
|
message (no editor) [fixup rebase-8]
|
|
message (no editor) [squash rebase-7]
|
|
HEAD [reword rebase-6]
|
|
message (no editor) [reword rebase-6]
|
|
message [squash rebase-5]
|
|
message (no editor) [fixup rebase-4]
|
|
message (no editor) [pick rebase-3]
|
|
message (no editor) [fixup rebase-2]
|
|
message (no editor) [fixup rebase-1]
|
|
merge [pick rebase-b]
|
|
message [pick rebase-a]
|