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

Re: [PATCH v4 5/7] builtin/tag: add --format argument for tag -v

From
Jeff King <peff@peff.net>
Date
Oct 19, 2016, 09:10 UTC
Message-ID
<20161019091044.k3ewbfxjj6ihv5o5@sigill.intra.peff.net>
In-Reply-To
<20161007210721.20437-6-santiago@nyu.edu>
On Fri, Oct 07, 2016 at 05:07:19PM -0400, santiago@nyu.edu wrote:
> Adding --format to git tag -v mutes the default output of the GPG
> verification and instead prints the formatted tag object.

The same comments apply to "mutes" here, as to the previous patch (which is to say I think we may want something more, but this is probably OK for now).

Show 10 quoted lines
> diff --git a/Documentation/git-tag.txt b/Documentation/git-tag.txt
> index 7ecca8e..3bb5e3c 100644
> --- a/Documentation/git-tag.txt
> +++ b/Documentation/git-tag.txt
> @@ -15,7 +15,7 @@ SYNOPSIS
>  'git tag' [-n[<num>]] -l [--contains <commit>] [--points-at <object>]
>  	[--column[=<options>] | --no-column] [--create-reflog] [--sort=<key>]
>  	[--format=<format>] [--[no-]merged [<commit>]] [<pattern>...]
> -'git tag' -v <tagname>...
> +'git tag' -v [--format=<format>] <tagname>...

Just thinking out loud, but if we had ref-filter placeholders that triggered GPG verification, you could do this all with the listing mode, like:

  git tag --format='%(gpgstatus) %(tag) %(refname:short)'
and verify multiple tags (or give a single tag to limit it to just one).

I don't think that's any kind of blocker for this series. We already have "-v", and adding --format to it is reasonable, even if we eventually move to a world where people can use the listing mode. Like I said, just thinking out loud.

Show 10 quoted lines
> +static int for_each_tag_name(const char **argv, each_tag_name_fn fn,
> +		void *cb_data)
>  {
>  	const char **p;
>  	char ref[PATH_MAX];
>  	int had_error = 0;
>  	unsigned char sha1[20];
>  
> +
>  	for (p = argv; *p; p++) {
Extra space?
Show 6 quoted lines
>  static int verify_tag(const char *name, const char *ref,
> -				const unsigned char *sha1)
> +				const unsigned char *sha1, void *cb_data)
>  {
> -	return verify_and_format_tag(sha1, name, NULL, GPG_VERIFY_VERBOSE);
> +	int flags;

Probably doesn't matter much, but these flags are defined as "unsigned" elsewhere.

-Peff
Previous: santiago@nyu.eduNext: santiago@nyu.edu
Message 12 of 16 in “Add --format to tag verification”
  1. 0/7 Add --format to tag verificationsantiago@nyu.edu, Oct 7, 2016
  2. 2/7 ref-filter: add function to print single ref_array_itemsantiago@nyu.edu, Oct 7, 2016
  3. Jeff KingOct 19, 2016
  4. Jeff KingOct 19, 2016
  5. Santiago TorresOct 19, 2016
  6. 4/7 builtin/verify-tag: add --format to verify-tagsantiago@nyu.edu, Oct 7, 2016
  7. Jeff KingOct 19, 2016
  8. 3/7 tag: add format specifier to gpg_verify_tagsantiago@nyu.edu, Oct 7, 2016
  9. 1/7 gpg-interface, tag: add GPG_VERIFY_QUIET flagsantiago@nyu.edu, Oct 7, 2016
  10. Jeff KingOct 19, 2016
  11. 5/7 builtin/tag: add --format argument for tag -vsantiago@nyu.edu, Oct 7, 2016
  12. Jeff KingOct 19, 2016
  13. 6/7 t/t7030-verify-tag: Add --format specifier testssantiago@nyu.edu, Oct 7, 2016
  14. Jeff KingOct 19, 2016
  15. 7/7 t/t7004-tag: Add --format specifier testssantiago@nyu.edu, Oct 7, 2016
  16. Santiago TorresOct 11, 2016

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.