# [PATCH 0/2] rebase --root: fix `reword` on a root commit 17 messages from 2018-06-16 to 2018-06-20. Participants: Johannes Schindelin via GitGitGadget, Todd Zullinger, Phillip Wood, Junio C Hamano, Johannes Schindelin. Thread: https://gitlist.dev/t/48722 ## Johannes Schindelin via GitGitGadget, 2018-06-16 19:26 Subject: [PATCH 0/2] rebase --root: fix `reword` on a root commit Message-ID: URL: https://gitlist.dev/e/pull.3.git.gitgitgadget%40gmail.com ``` From: GitGitGadget Todd Zullinger reported this bug in https://public-inbox.org/git/20180615043111.GS3094@zaya.teonanacatl.net/: when calling git rebase --root and trying to reword the root commit's message, a BUG is reported. This fixes that. IMO the bug fix is trivial enough to qualify for inclusion into v2.18.0, still. Johannes Schindelin (1): rebase --root: fix amending root commit messages Todd Zullinger (1): rebase --root: demonstrate a bug while amending root commit messages sequencer.c | 2 +- t/t3404-rebase-interactive.sh | 9 +++++++++ 2 files changed, 10 insertions(+), 1 deletion(-) base-commit: 68372c88794aba15f853542008cda39def768372 -- 2.17.0.windows.1 ``` ## Johannes Schindelin via GitGitGadget, 2018-06-15 04:31 Subject: [PATCH 1/2] rebase --root: demonstrate a bug while amending root commit messages Message-ID: URL: https://gitlist.dev/e/d59805a43ddaf4bbd4528a2b7afa9809eca9b86b.1529177176.git.gitgitgadget%40gmail.com In-Reply-To: ``` From: Todd Zullinger When splitting a repository, running `git rebase -i --root` to reword the initial commit, Git dies with BUG: sequencer.c:795: root commit without message. Signed-off-by: Todd Zullinger Signed-off-by: Johannes Schindelin --- t/t3404-rebase-interactive.sh | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/t/t3404-rebase-interactive.sh b/t/t3404-rebase-interactive.sh index c65826dda..ca94c688d 100755 --- a/t/t3404-rebase-interactive.sh +++ b/t/t3404-rebase-interactive.sh @@ -971,6 +971,15 @@ test_expect_success 'rebase -i --root fixup root commit' ' test 0 = $(git cat-file commit HEAD | grep -c ^parent\ ) ' +test_expect_failure 'rebase -i --root reword root commit' ' + test_when_finished "test_might_fail git rebase --abort" && + git checkout -b reword-root-branch master && + set_fake_editor && + FAKE_LINES="reword 1 2" FAKE_COMMIT_MESSAGE="A changed" \ + git rebase -i --root && + git show HEAD^ | grep "A changed" +' + test_expect_success C_LOCALE_OUTPUT 'rebase --edit-todo does not work on non-interactive rebase' ' git reset --hard && git checkout conflict-branch && -- 2.17.0.windows.1 ``` ## Johannes Schindelin via GitGitGadget, 2018-06-16 19:00 Subject: [PATCH 2/2] rebase --root: fix amending root commit messages Message-ID: <6f492ded5c4b9ee82501433d5a5227bc3e546c31.1529177176.git.gitgitgadget@gmail.com> URL: https://gitlist.dev/e/6f492ded5c4b9ee82501433d5a5227bc3e546c31.1529177176.git.gitgitgadget%40gmail.com In-Reply-To: ``` From: Johannes Schindelin The code path that triggered that "BUG" really does not want to run without an explicit commit message. In the case where we want to amend a commit message, we have an *implicit* commit message, though: the one of the commit to amend. Therefore, this code path should not even be entered. Signed-off-by: Johannes Schindelin --- sequencer.c | 2 +- t/t3404-rebase-interactive.sh | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/sequencer.c b/sequencer.c index cca968043..4034c0461 100644 --- a/sequencer.c +++ b/sequencer.c @@ -784,7 +784,7 @@ static int run_git_commit(const char *defmsg, struct replay_opts *opts, struct child_process cmd = CHILD_PROCESS_INIT; const char *value; - if (flags & CREATE_ROOT_COMMIT) { + if ((flags & CREATE_ROOT_COMMIT) && !(flags & AMEND_MSG)) { struct strbuf msg = STRBUF_INIT, script = STRBUF_INIT; const char *author = is_rebase_i(opts) ? read_author_ident(&script) : NULL; diff --git a/t/t3404-rebase-interactive.sh b/t/t3404-rebase-interactive.sh index ca94c688d..e500d7c32 100755 --- a/t/t3404-rebase-interactive.sh +++ b/t/t3404-rebase-interactive.sh @@ -971,7 +971,7 @@ test_expect_success 'rebase -i --root fixup root commit' ' test 0 = $(git cat-file commit HEAD | grep -c ^parent\ ) ' -test_expect_failure 'rebase -i --root reword root commit' ' +test_expect_success 'rebase -i --root reword root commit' ' test_when_finished "test_might_fail git rebase --abort" && git checkout -b reword-root-branch master && set_fake_editor && -- 2.17.0.windows.1 ``` ## Todd Zullinger, 2018-06-16 20:11 Subject: Re: [PATCH 0/2] rebase --root: fix `reword` on a root commit Message-ID: <20180616201143.GH11827@zaya.teonanacatl.net> URL: https://gitlist.dev/e/20180616201143.GH11827%40zaya.teonanacatl.net In-Reply-To: ``` Hi Johannes, Johannes Schindelin via GitGitGadget wrote: > From: GitGitGadget > > Todd Zullinger reported this bug in > https://public-inbox.org/git/20180615043111.GS3094@zaya.teonanacatl.net/: > when calling git rebase --root and trying to reword the > root commit's message, a BUG is reported. > > This fixes that. > > IMO the bug fix is trivial enough to qualify for inclusion into v2.18.0, still. It does indeed fix the issue. I agree it would be nice to see it in 2.18.0. As a fix for a minor regression introduced in this cycle, that seems reasonable. > Johannes Schindelin (1): > rebase --root: fix amending root commit messages > > Todd Zullinger (1): > rebase --root: demonstrate a bug while amending root commit messages > > sequencer.c | 2 +- > t/t3404-rebase-interactive.sh | 9 +++++++++ > 2 files changed, 10 insertions(+), 1 deletion(-) > > > base-commit: 68372c88794aba15f853542008cda39def768372 -- Todd ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ I don't mean to sound cold, or cruel, or vicious, but I am, so that's the way it comes out. -- Bill Hicks ``` ## Phillip Wood, 2018-06-18 10:25 Subject: Re: [PATCH 1/2] rebase --root: demonstrate a bug while amending rootcommit messages Message-ID: <484fe825-0726-a027-1187-de00df6406d5@talktalk.net> URL: https://gitlist.dev/e/484fe825-0726-a027-1187-de00df6406d5%40talktalk.net In-Reply-To: ``` Hi Todd/Johannes On 15/06/18 05:31, Johannes Schindelin via GitGitGadget wrote: > > From: Todd Zullinger > > When splitting a repository, running `git rebase -i --root` to reword > the initial commit, Git dies with > > BUG: sequencer.c:795: root commit without message. > > Signed-off-by: Todd Zullinger > Signed-off-by: Johannes Schindelin > --- > t/t3404-rebase-interactive.sh | 9 +++++++++ > 1 file changed, 9 insertions(+) > > diff --git a/t/t3404-rebase-interactive.sh b/t/t3404-rebase-interactive.sh > index c65826dda..ca94c688d 100755 > --- a/t/t3404-rebase-interactive.sh > +++ b/t/t3404-rebase-interactive.sh > @@ -971,6 +971,15 @@ test_expect_success 'rebase -i --root fixup root commit' ' > test 0 = $(git cat-file commit HEAD | grep -c ^parent\ ) > ' > > +test_expect_failure 'rebase -i --root reword root commit' ' > + test_when_finished "test_might_fail git rebase --abort" && > + git checkout -b reword-root-branch master && > + set_fake_editor && > + FAKE_LINES="reword 1 2" FAKE_COMMIT_MESSAGE="A changed" \ > + git rebase -i --root && > + git show HEAD^ | grep "A changed" I wonder if it should also check that HEAD^ is the root commit, to make sure that the squash-onto commit that's created and then amended has been squashed onto. Best Wishes Phillip > +' > + > test_expect_success C_LOCALE_OUTPUT 'rebase --edit-todo does not work on non-interactive rebase' ' > git reset --hard && > git checkout conflict-branch && > ``` ## Junio C Hamano, 2018-06-18 16:21 Subject: Re: [PATCH 0/2] rebase --root: fix `reword` on a root commit Message-ID: URL: https://gitlist.dev/e/xmqqd0woxdz9.fsf%40gitster-ct.c.googlers.com In-Reply-To: <20180616201143.GH11827@zaya.teonanacatl.net> ``` Todd Zullinger writes: > Hi Johannes, > > Johannes Schindelin via GitGitGadget wrote: >> From: GitGitGadget >> >> Todd Zullinger reported this bug in >> https://public-inbox.org/git/20180615043111.GS3094@zaya.teonanacatl.net/: >> when calling git rebase --root and trying to reword the >> root commit's message, a BUG is reported. >> >> This fixes that. >> >> IMO the bug fix is trivial enough to qualify for inclusion into v2.18.0, still. > > It does indeed fix the issue. I agree it would be nice to > see it in 2.18.0. As a fix for a minor regression > introduced in this cycle, that seems reasonable. Offhand it is not clear from the proposed log message where the original breakage happened, but if this is to fix a regression between v2.17.0 and v2.18.0, then let's have it. As -rc2 slipped for a few days, it is reasonable to delay the final by a couple of days as well, if only to give the last minute fixes and translators reasonable time to breathe. Thanks. > >> Johannes Schindelin (1): >> rebase --root: fix amending root commit messages >> >> Todd Zullinger (1): >> rebase --root: demonstrate a bug while amending root commit messages >> >> sequencer.c | 2 +- >> t/t3404-rebase-interactive.sh | 9 +++++++++ >> 2 files changed, 10 insertions(+), 1 deletion(-) >> >> >> base-commit: 68372c88794aba15f853542008cda39def768372 ``` ## Todd Zullinger, 2018-06-18 16:41 Subject: Re: [PATCH 0/2] rebase --root: fix `reword` on a root commit Message-ID: <20180618164140.GN11827@zaya.teonanacatl.net> URL: https://gitlist.dev/e/20180618164140.GN11827%40zaya.teonanacatl.net In-Reply-To: ``` Hi, Junio C Hamano wrote: > Todd Zullinger writes: > >> Hi Johannes, >> >> Johannes Schindelin via GitGitGadget wrote: >>> From: GitGitGadget >>> >>> Todd Zullinger reported this bug in >>> https://public-inbox.org/git/20180615043111.GS3094@zaya.teonanacatl.net/: >>> when calling git rebase --root and trying to reword the >>> root commit's message, a BUG is reported. >>> >>> This fixes that. >>> >>> IMO the bug fix is trivial enough to qualify for inclusion into v2.18.0, still. >> >> It does indeed fix the issue. I agree it would be nice to >> see it in 2.18.0. As a fix for a minor regression >> introduced in this cycle, that seems reasonable. > > Offhand it is not clear from the proposed log message where the > original breakage happened, but if this is to fix a regression > between v2.17.0 and v2.18.0, then let's have it. As -rc2 slipped > for a few days, it is reasonable to delay the final by a couple of > days as well, if only to give the last minute fixes and translators > reasonable time to breathe. Perhaps replacing the first paragraph with this would make it clearer? Since 21d0764c82 ("rebase -i --root: let the sequencer handle even the initial part", 2018-05-04), when splitting a repository, running `git rebase -i --root` to reword the initial commit, Git dies with Alternately, a similar note could be added at the end. This regression was recently introduced in 21d0764c82 ("rebase -i --root: let the sequencer handle even the initial part", 2018-05-04). -- Todd ``` ## Todd Zullinger, 2018-06-18 16:49 Subject: Re: [PATCH 1/2] rebase --root: demonstrate a bug while amending rootcommit messages Message-ID: <20180618164958.GO11827@zaya.teonanacatl.net> URL: https://gitlist.dev/e/20180618164958.GO11827%40zaya.teonanacatl.net In-Reply-To: <484fe825-0726-a027-1187-de00df6406d5@talktalk.net> ``` Hi Phillip, Phillip Wood wrote: > On 15/06/18 05:31, Johannes Schindelin via GitGitGadget wrote: >> >> From: Todd Zullinger >> >> +test_expect_failure 'rebase -i --root reword root commit' ' >> + test_when_finished "test_might_fail git rebase --abort" && >> + git checkout -b reword-root-branch master && >> + set_fake_editor && >> + FAKE_LINES="reword 1 2" FAKE_COMMIT_MESSAGE="A changed" \ >> + git rebase -i --root && >> + git show HEAD^ | grep "A changed" > > I wonder if it should also check that HEAD^ is the root commit, to make > sure that the squash-onto commit that's created and then amended has > been squashed onto. Hmm, is that something which other tests don't cover or an issue that could affect 'rebase -i --root' with reword differently than other 'rebase -i' commands? I admit I'm not well-versed in the rebase -i tests and I focused only on creating a test which demonstrated the bug I noticed. -- Todd ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The average woman would rather be beautiful than smart because the average man can see better than he can think. ``` ## Junio C Hamano, 2018-06-18 19:25 Subject: Re: [PATCH 0/2] rebase --root: fix `reword` on a root commit Message-ID: URL: https://gitlist.dev/e/xmqq8t7byk19.fsf%40gitster-ct.c.googlers.com In-Reply-To: <20180618164140.GN11827@zaya.teonanacatl.net> ``` Todd Zullinger writes: >> Offhand it is not clear from the proposed log message where the >> original breakage happened, but if this is to fix a regression >> between v2.17.0 and v2.18.0, then let's have it. As -rc2 slipped >> for a few days, it is reasonable to delay the final by a couple of >> days as well, if only to give the last minute fixes and translators >> reasonable time to breathe. > > Perhaps replacing the first paragraph with this would make > it clearer? > > Since 21d0764c82 ("rebase -i --root: let the sequencer handle even the > initial part", 2018-05-04), when splitting a repository, running `git > rebase -i --root` to reword the initial commit, Git dies with > > Alternately, a similar note could be added at the end. > > This regression was recently introduced in 21d0764c82 ("rebase -i > --root: let the sequencer handle even the initial part", 2018-05-04). These certainly are ways to require one less hop to the readers than the original ;-) Having said that, I've already merged it down to 'next' and want to have these in 'master' before final, so no need to further fix-up the log message anymore. Thanks. ``` ## Johannes Schindelin, 2018-06-18 21:46 Subject: Re: [PATCH 1/2] rebase --root: demonstrate a bug while amending rootcommit messages Message-ID: URL: https://gitlist.dev/e/nycvar.QRO.7.76.6.1806182343421.77%40tvgsbejvaqbjf.bet In-Reply-To: <20180618164958.GO11827@zaya.teonanacatl.net> ``` Hi Todd, On Mon, 18 Jun 2018, Todd Zullinger wrote: > Phillip Wood wrote: > > On 15/06/18 05:31, Johannes Schindelin via GitGitGadget wrote: > >> > >> From: Todd Zullinger > >> > >> +test_expect_failure 'rebase -i --root reword root commit' ' > >> + test_when_finished "test_might_fail git rebase --abort" && > >> + git checkout -b reword-root-branch master && > >> + set_fake_editor && > >> + FAKE_LINES="reword 1 2" FAKE_COMMIT_MESSAGE="A changed" \ > >> + git rebase -i --root && > >> + git show HEAD^ | grep "A changed" > > > > I wonder if it should also check that HEAD^ is the root commit, to make > > sure that the squash-onto commit that's created and then amended has > > been squashed onto. > > Hmm, is that something which other tests don't cover or an > issue that could affect 'rebase -i --root' with reword > differently than other 'rebase -i' commands? > > I admit I'm not well-versed in the rebase -i tests and I > focused only on creating a test which demonstrated the bug I > noticed. I think we should test this here, to make sure it is tested, and it should be as easy as: test -z "$(git show -s --format=%p HEAD^)" Hopefully you beat me to it, otherwise I will try to take care of this tomorrow. Ciao, Dscho ``` ## Todd Zullinger, 2018-06-18 22:19 Subject: [PATCH] t3404: check root commit in 'rebase -i --root reword root commit' Message-ID: <20180618221942.GQ11827@zaya.teonanacatl.net> URL: https://gitlist.dev/e/20180618221942.GQ11827%40zaya.teonanacatl.net In-Reply-To: ``` When testing a reworded root commit, ensure that the squash-onto commit which is created and amended is still the root commit. Suggested-by: Phillip Wood Helped-by: Johannes Schindelin Signed-off-by: Todd Zullinger --- Hi Johannes, Johannes Schindelin wrote: >On Mon, 18 Jun 2018, Todd Zullinger wrote: >> Phillip Wood wrote: >>> On 15/06/18 05:31, Johannes Schindelin via GitGitGadget wrote: >>>> >>>> From: Todd Zullinger >>>> >>>> +test_expect_failure 'rebase -i --root reword root commit' ' >>>> + test_when_finished "test_might_fail git rebase --abort" && >>>> + git checkout -b reword-root-branch master && >>>> + set_fake_editor && >>>> + FAKE_LINES="reword 1 2" FAKE_COMMIT_MESSAGE="A changed" \ >>>> + git rebase -i --root && >>>> + git show HEAD^ | grep "A changed" >>> >>> I wonder if it should also check that HEAD^ is the root commit, to make >>> sure that the squash-onto commit that's created and then amended has >>> been squashed onto. >> >> Hmm, is that something which other tests don't cover or an >> issue that could affect 'rebase -i --root' with reword >> differently than other 'rebase -i' commands? >> >> I admit I'm not well-versed in the rebase -i tests and I >> focused only on creating a test which demonstrated the bug I >> noticed. > > I think we should test this here, to make sure it is tested, and it should > be as easy as: > > test -z "$(git show -s --format=%p HEAD^)" > > Hopefully you beat me to it, otherwise I will try to take care of this > tomorrow. With luck, this will save you a few minutes, assuming the commit message is reasonable (or can be improved with help from Phillip and others). :) Or Junio may just squash this onto js/rebase-i-root-fix. Thanks. t/t3404-rebase-interactive.sh | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/t/t3404-rebase-interactive.sh b/t/t3404-rebase-interactive.sh index e500d7c320..352a52e59d 100755 --- a/t/t3404-rebase-interactive.sh +++ b/t/t3404-rebase-interactive.sh @@ -977,7 +977,8 @@ test_expect_success 'rebase -i --root reword root commit' ' set_fake_editor && FAKE_LINES="reword 1 2" FAKE_COMMIT_MESSAGE="A changed" \ git rebase -i --root && - git show HEAD^ | grep "A changed" + git show HEAD^ | grep "A changed" && + test -z "$(git show -s --format=%p HEAD^)" ' test_expect_success C_LOCALE_OUTPUT 'rebase --edit-todo does not work on non-interactive rebase' ' -- Todd ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Anyone who is capable of getting themselves made President should on no account be allowed to do the job. -- Douglas Adams, "The Hitchhiker's Guide to the Galaxy" ``` ## Johannes Schindelin, 2018-06-19 06:54 Subject: Re: [PATCH] t3404: check root commit in 'rebase -i --root reword root commit' Message-ID: URL: https://gitlist.dev/e/nycvar.QRO.7.76.6.1806190853450.77%40tvgsbejvaqbjf.bet In-Reply-To: <20180618221942.GQ11827@zaya.teonanacatl.net> ``` Hi Todd, On Mon, 18 Jun 2018, Todd Zullinger wrote: > When testing a reworded root commit, ensure that the squash-onto commit > which is created and amended is still the root commit. > > Suggested-by: Phillip Wood > Helped-by: Johannes Schindelin > Signed-off-by: Todd Zullinger Trusting that this test passes: ACK! Ciao, Dscho ``` ## Junio C Hamano, 2018-06-19 16:00 Subject: Re: [PATCH] t3404: check root commit in 'rebase -i --root reword root commit' Message-ID: URL: https://gitlist.dev/e/xmqqin6ewyv2.fsf%40gitster-ct.c.googlers.com In-Reply-To: <20180618221942.GQ11827@zaya.teonanacatl.net> ``` Todd Zullinger writes: > With luck, this will save you a few minutes, assuming the > commit message is reasonable (or can be improved with help > from Phillip and others). :) OK. > Or Junio may just squash this onto js/rebase-i-root-fix. Nah, not for a hotfix on the last couple of days before the final. We'd need to build on top, not "squash". > > Thanks. > > t/t3404-rebase-interactive.sh | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) > > diff --git a/t/t3404-rebase-interactive.sh b/t/t3404-rebase-interactive.sh > index e500d7c320..352a52e59d 100755 > --- a/t/t3404-rebase-interactive.sh > +++ b/t/t3404-rebase-interactive.sh > @@ -977,7 +977,8 @@ test_expect_success 'rebase -i --root reword root commit' ' > set_fake_editor && > FAKE_LINES="reword 1 2" FAKE_COMMIT_MESSAGE="A changed" \ > git rebase -i --root && > - git show HEAD^ | grep "A changed" > + git show HEAD^ | grep "A changed" && > + test -z "$(git show -s --format=%p HEAD^)" > ' > > test_expect_success C_LOCALE_OUTPUT 'rebase --edit-todo does not work on non-interactive rebase' ' ``` ## Junio C Hamano, 2018-06-19 16:21 Subject: Re: [PATCH] t3404: check root commit in 'rebase -i --root reword root commit' Message-ID: URL: https://gitlist.dev/e/xmqqa7rqwxuz.fsf%40gitster-ct.c.googlers.com In-Reply-To: <20180618221942.GQ11827@zaya.teonanacatl.net> ``` Todd Zullinger writes: > index e500d7c320..352a52e59d 100755 > --- a/t/t3404-rebase-interactive.sh > +++ b/t/t3404-rebase-interactive.sh > @@ -977,7 +977,8 @@ test_expect_success 'rebase -i --root reword root commit' ' > set_fake_editor && > FAKE_LINES="reword 1 2" FAKE_COMMIT_MESSAGE="A changed" \ > git rebase -i --root && > - git show HEAD^ | grep "A changed" > + git show HEAD^ | grep "A changed" && > + test -z "$(git show -s --format=%p HEAD^)" > ' The additional test probably will pass when HEAD is a root commit by failing to refer to HEAD^, resulting an empty output from show. The previous step would also give an error and won't emit anything that would match "A changed", so it probably is OK, though. ``` ## Todd Zullinger, 2018-06-19 19:12 Subject: Re: [PATCH] t3404: check root commit in 'rebase -i --root reword root commit' Message-ID: <20180619191253.GR11827@zaya.teonanacatl.net> URL: https://gitlist.dev/e/20180619191253.GR11827%40zaya.teonanacatl.net In-Reply-To: ``` Junio C Hamano wrote: > Todd Zullinger writes: >> Or Junio may just squash this onto js/rebase-i-root-fix. > > Nah, not for a hotfix on the last couple of days before the final. > We'd need to build on top, not "squash". Indeed. I somehow missed that you'd merged and pushed the changes to master and next when I set this. I was mistakenly thinking it was only on the js/rebase-i-root-fix integration branch. Thanks, -- Todd ``` ## Johannes Schindelin, 2018-06-20 11:03 Subject: Re: [PATCH] t3404: check root commit in 'rebase -i --root reword root commit' Message-ID: URL: https://gitlist.dev/e/nycvar.QRO.7.76.6.1806201301530.11870%40tvgsbejvaqbjf.bet In-Reply-To: ``` Hi Junio, On Tue, 19 Jun 2018, Junio C Hamano wrote: > Todd Zullinger writes: > > > With luck, this will save you a few minutes, assuming the > > commit message is reasonable (or can be improved with help > > from Phillip and others). :) > > OK. > > > Or Junio may just squash this onto js/rebase-i-root-fix. > > Nah, not for a hotfix on the last couple of days before the final. > We'd need to build on top, not "squash". Right. Can we take this on top, at a leisurely pace? I mean: we verified that this works in the upcoming v2.18.0, and it would be nice to have that extra regression test safety in the future, but it is not crucial to include it in v2.18.0 itself. Ciao, Dscho ``` ## Johannes Schindelin, 2018-06-20 11:04 Subject: Re: [PATCH] t3404: check root commit in 'rebase -i --root reword root commit' Message-ID: URL: https://gitlist.dev/e/nycvar.QRO.7.76.6.1806201303560.11870%40tvgsbejvaqbjf.bet In-Reply-To: ``` Hi Junio, On Tue, 19 Jun 2018, Junio C Hamano wrote: > Todd Zullinger writes: > > > index e500d7c320..352a52e59d 100755 > > --- a/t/t3404-rebase-interactive.sh > > +++ b/t/t3404-rebase-interactive.sh > > @@ -977,7 +977,8 @@ test_expect_success 'rebase -i --root reword root commit' ' > > set_fake_editor && > > FAKE_LINES="reword 1 2" FAKE_COMMIT_MESSAGE="A changed" \ > > git rebase -i --root && > > - git show HEAD^ | grep "A changed" > > + git show HEAD^ | grep "A changed" && > > + test -z "$(git show -s --format=%p HEAD^)" > > ' > > The additional test probably will pass when HEAD is a root commit by > failing to refer to HEAD^, resulting an empty output from show. The > previous step would also give an error and won't emit anything that > would match "A changed", so it probably is OK, though. That matches my thinking. Otherwise, we would have had to do the git show -s --format=%p HEAD^ >out && test_must_be_empty out dance. Ciao, Dscho ```