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

Re: [PATCH 1/1] notes: copy notes to HEAD by default

From
Junio C Hamano <gitster@pobox.com>
Date
Oct 16, 2019, 02:01 UTC
Message-ID
<xmqqpnixa1oh.fsf@gitster-ct.c.googlers.com>
In-Reply-To
<20191015163631.21808-2-congdanhqx@gmail.com>
Doan Tran Cong Danh <congdanhqx@gmail.com> writes:
Show 5 quoted lines
> The target objects for copying notes was defaulted to HEAD from very
> early stage of git-notes.
>
> However, that default was limited by commit bbb1b8a35a, ("notes: check
> number of parameters to "git notes copy"", 2010-06-28).

Sorry, I don't quite get the above. The said commit made sure 'git notes copy' gets the right number of arguments, saying """Otherwise we may segfault with too few parameters.""" I take that as a sign that before that commit it was not defaulting to HEAD but attempting to access the missing argv[2] (or whatever the index the <to-object> should be at) and dereferencing a NULL?

    ... goes and digs ...

I think v1.6.6.1-458-g74884b524e is the commit that made the command line parsing into the current shape, i.e. one parse_options() call in each of the subcommand that gets dispatched, and you are right that with that version a single argument given on the command line is taken as the <from-object> and <to-object> defaults to HEAD.

So... what happend between that vesrion and v1.7.1-200-gbbb1b8a35a?
    ... goes and looks at bbb1b8a35a again ...

Ah, I think there is an off-by-one. When not from-stdin and not using rewrite-cmd, before that patch, we did not even check if from-obj exists, so in that sense, the commit had a right idea that it must check for "too few parameters", but it shouldn't have insisted that we have at least two. It is OK to have just one, i.e. only the from-obj, for our purpose.

Show 8 quoted lines
>  copy::
> -	Copy the notes for the first object onto the second object.
> -	Abort if the second object already has notes, or if the first
> +	Copy the notes for the first object onto the second object (defaults to
> +	HEAD). Abort if the second object already has notes, or if the first
>  	object has none (use -f to overwrite existing notes to the
>  	second object). This subcommand is equivalent to:
>  	`git notes add [-f] -C $(git notes list <from-object>) <to-object>`
This is OK.
Show 13 quoted lines
> diff --git a/builtin/notes.c b/builtin/notes.c
> index 02e97f55c5..95456f3165 100644
> --- a/builtin/notes.c
> +++ b/builtin/notes.c
> @@ -513,7 +513,7 @@ static int copy(int argc, const char **argv, const char *prefix)
>  		}
>  	}
>  
> -	if (argc < 2) {
> +	if (argc < 1) {
>  		error(_("too few parameters"));
>  		usage_with_options(git_notes_copy_usage, options);
>  	}
So is this.
Show 14 quoted lines
> diff --git a/t/t3301-notes.sh b/t/t3301-notes.sh
> index d3fa298c6a..a8f9a0f36c 100755
> --- a/t/t3301-notes.sh
> +++ b/t/t3301-notes.sh
> @@ -908,6 +908,10 @@ test_expect_success 'allow overwrite with "git notes copy -f"' '
>  	git notes copy -f HEAD~2 HEAD &&
>  	git log -1 >actual &&
>  	test_cmp expect actual &&
> +	test "$(git notes list HEAD)" = "$(git notes list HEAD~2)" &&
> +	git notes copy -f HEAD~2 &&
> +	git log -1 >actual &&
> +	test_cmp expect actual &&
>  	test "$(git notes list HEAD)" = "$(git notes list HEAD~2)"
>  '

This I am not sure is a good test to add to, especially as a fix to bbb1b8a, which added this test:

diff --git a/t/t3301-notes.sh b/t/t3301-notes.sh
index 64f32ad94d..2d67a40fc1 100755
--- a/t/t3301-notes.sh
+++ b/t/t3301-notes.sh
@@ -1044,4 +1044,10 @@ test_expect_success 'GIT_NOTES_REWRITE_REF overrides config' '
 	git log -1 > output &&
 	test_cmp expect output
 '
+
+test_expect_success 'git notes copy diagnoses too many or too few parameters' '
+	test_must_fail git notes copy &&
+	test_must_fail git notes copy one two three
+'
+
 test_done

The lack of testing that "git notes copy <from-obj>" succeeding is
why the off-by-one bug was not noticed, so I think that test (which
still exists to this day) is the right place to add a test to
protect this fix.

As to the log message, here is how I would explain/justify the
change, if I were writing it.

	notes: fix minimum number of parameters to "copy" subcommand

	The builtin/notes.::copy() function is prepared to handle
	only one argument given from the command line; in such a
	case, to-obj defaults to HEAD.

	When bbb1b8a3 ("notes: check number of parameters to "git
	notes copy"", 2010-06-28) tried to make sure "git notes
	copy" (with *no* other argument) does not dereference NULL
	by making sure we did not get too few parameters, it
	incorrectly insisted that we get two arguments, instead of
	just one.  This disabled the defaulting to-obj to HEAD.
	Correct it.

Thanks.
Previous: Doan Tran Cong DanhNext: Danh Doan
Message 3 of 8 in “Allow default value for target of git-notes copy”
  1. 0/1 Allow default value for target of git-notes copyDoan Tran Cong Danh, Oct 15, 2019
  2. 1/1 notes: copy notes to HEAD by defaultDoan Tran Cong Danh, Oct 15, 2019
  3. Junio C HamanoOct 16, 2019
  4. Danh DoanOct 16, 2019
  5. 1/2 t3301: test diagnose messages for too few/many paramtersDoan Tran Cong Danh, Oct 16, 2019
  6. 2/2 notes: fix minimum number of parameters to "copy" subcommandDoan Tran Cong Danh, Oct 16, 2019
  7. Junio C HamanoOct 18, 2019
  8. Junio C HamanoOct 18, 2019

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.