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

Re: [PATCH] rebase -i: fix rewording with --committer-date-is-author-date

From
Jeff King <peff@peff.net>
Date
Nov 2, 2021, 22:32 UTC
Message-ID
<YYG8aq85UmMMVW4l@coredump.intra.peff.net>
In-Reply-To
<pull.1123.git.git.1635883844710.gitgitgadget@gmail.com>
On Tue, Nov 02, 2021 at 08:10:44PM +0000, Phillip Wood via GitGitGadget wrote:
Show 10 quoted lines
> From: Phillip Wood <phillip.wood@dunelm.org.uk>
> 
> baf8ec8d3a (rebase -r: don't write .git/MERGE_MSG when
> fast-forwarding, 2021-08-20) stopped reading the author script in
> run_git_commit() when rewording a commit. This is normally safe
> because "git commit --amend" preserves the authorship. However if the
> user passes "--committer-date-is-author-date" then we need to read the
> author date from the author script when rewording. Fix this regression
> by tightening the check for when it is safe to skip reading the author
> script.

That description makes sense, and the patch matches. Not being that familiar with this area, my biggest question would be: are there are other cases that would need the same treatment? And is there a way we can make it easier to avoid forgetting such a case in the future?

Show 14 quoted lines
> diff --git a/sequencer.c b/sequencer.c
> index cd2aabf1f76..ea96837cde3 100644
> --- a/sequencer.c
> +++ b/sequencer.c
> @@ -997,7 +997,9 @@ static int run_git_commit(const char *defmsg,
>  
>  	cmd.git_cmd = 1;
>  
> -	if (is_rebase_i(opts) && !(!defmsg && (flags & AMEND_MSG)) &&
> +	if (is_rebase_i(opts) &&
> +	    ((opts->committer_date_is_author_date && !opts->ignore_date) ||
> +	     !(!defmsg && (flags & AMEND_MSG))) &&
>  	    read_env_script(&cmd.env_array)) {
>  		const char *gpg_opt = gpg_sign_opt_quoted(opts);

This conditional is getting pretty complicated. I wonder if a helper like:

  if (is_rebase_i(opts) && !needs_env_script(...))

might help, but I guess it needs a funky array of inputs (defmsg, flags, and opts). So maybe it is just making things worse.

Show 13 quoted lines
> +test_expect_success '--committer-date-is-author-date works when rewording' '
> +	GIT_AUTHOR_DATE="@1234 +0300" git commit --amend --reset-author &&
> +	(
> +		set_fake_editor &&
> +		FAKE_COMMIT_MESSAGE=edited \
> +			FAKE_LINES="reword 1" \
> +			git rebase -i --committer-date-is-author-date HEAD^
> +	) &&
> +	test_write_lines edited "" >expect &&
> +	git log --format="%B" -1 >actual &&
> +	test_cmp expect actual &&
> +	test_ctime_is_atime -1
> +'

This test make sense (I had to look up what "-1" means for test_ctime_is_atime; it's passed to git-log to decide which commits to look at).

Show 14 quoted lines
> +test_expect_success 'reset-author-date with --committer-date-is-author-date works when rewording' '
> +	GIT_AUTHOR_DATE="@1234 +0300" git commit --amend --reset-author &&
> +	(
> +		set_fake_editor &&
> +		FAKE_COMMIT_MESSAGE=edited \
> +			FAKE_LINES="reword 1" \
> +			git rebase -i --committer-date-is-author-date \
> +				--reset-author-date HEAD^
> +	) &&
> +	test_write_lines edited "" >expect &&
> +	git log --format="%B" -1 >actual &&
> +	test_cmp expect actual &&
> +	test_atime_is_ignored -1
> +'

And this one I guess is covering the --ignore-date cut-out in the code? I think it would pass even without it, as that is just noting a case where we _don't_ need to call read_env_script(). But I don't know if there is any user-visible effect of accidentally calling it when we don't need to (my impression is that it's just a performance thing).

-Peff
Previous: Phillip Wood via GitGitGadgetNext: Phillip Wood
Message 5 of 10 in “rebase -i: fix rewording with --committer-date-is-author-date”
  1. rebase -i: fix rewording with --committer-date-is-author-datePhillip Wood via GitGitGadget, Nov 2, 2021
  2. Eric SunshineNov 2, 2021
  3. Phillip WoodNov 2, 2021
  4. rebase -i: fix rewording with --committer-date-is-author-datePhillip Wood via GitGitGadget, Nov 2, 2021
  5. Jeff KingNov 2, 2021
  6. Phillip WoodNov 3, 2021
  7. Jeff KingNov 3, 2021
  8. Junio C HamanoNov 3, 2021
  9. Jeff KingNov 4, 2021
  10. Junio C HamanoNov 4, 2021

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.