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

Re: [PATCH 1/5] tag -v: use ‘git verify-tag’ without dash

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Mar 20, 2010, 21:29 UTC
Message-ID
<20100320212932.GA30010@progeny.tock>
In-Reply-To
<201003201701.16820.j6t@kdbg.org>
Johannes Sixt wrote:
> On Samstag, 20. März 2010, Jonathan Nieder wrote:
Show 11 quoted lines
>> -	const char *argv_verify_tag[] = {"git-verify-tag",
>> +	const char *argv_verify_tag[] = {"git", "verify-tag",
>>  					"-v", "SHA1_HEX", NULL};
>> -	argv_verify_tag[2] = sha1_to_hex(sha1);
>> +	argv_verify_tag[3] = sha1_to_hex(sha1);
>>
>>  	if (run_command_v_opt(argv_verify_tag, 0))
>>  		return error("could not verify the tag '%s'", name);
>
> This should rather be changed to run_command_v_opt(..., RUN_GIT_CMD). See 
> other examples in the code.
Neat.  Thanks for the pointer.
> Oh, you remove this in a later patch. Then why have this patch at all?

If the rest of the patches go in the right direction, this one should be dropped. I should presented it as two alternative series instead: one that follows the appropriate calling convention here, and one that libifies verify_tag.

In other words, no good reason at all; thanks for pointing it out. I’ll send a version of patch 4/5 that doesn’t depend on this one in a moment.

Jonathan
Previous: Johannes SixtNext: Jonathan Nieder
Message 4 of 9 in “libify verify_tag()”
  1. 0/5 libify verify_tag()Jonathan Nieder, Mar 20, 2010
  2. 1/5 tag -v: use ‘git verify-tag’ without dashJonathan Nieder, Mar 20, 2010
  3. Johannes SixtMar 20, 2010
  4. Jonathan NiederMar 20, 2010
  5. 2/5 verify-tag: use sigchain library to block SIGPIPEJonathan Nieder, Mar 20, 2010
  6. 3/5 Expose verify_tag()Jonathan Nieder, Mar 20, 2010
  7. 4/5 tag -v: Do not spawn a separate process for verify-tagJonathan Nieder, Mar 20, 2010
  8. 4/5 tag -v: Do not spawn a separate process for verify-tagJonathan Nieder, Mar 20, 2010
  9. 5/5 verify_tag_signature(): let caller look up tag object sha1Jonathan Nieder, Mar 20, 2010

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.