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

Re: [RFC/PATCH] verify-tag: add --check-name flag

From
Junio C Hamano <gitster@pobox.com>
Date
Jun 8, 2016, 18:43 UTC
Message-ID
<xmqqk2hzldx8.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<20160608142132.GA32299@LykOS.localdomain>
Santiago Torres <santiago@nyu.edu> writes:
Show 9 quoted lines
> Sorry I'm trying to follow this. Would it be best to then have
>
>     verify-tag [--check-name=tagname] (tag-ref|tag-name|sha1)?
>
> and
>
>     tag -v [--check-name] (tag-name)
>
> Or would --format still work better?

No matter what you do, don't call that "--check-name". It does not tell the users what aspect of that thing is "checked". Avoid being asked "Does this check tagname to make sure it does not have non-ASCII letters?", in other words.

As a longer-term direction, I think the best one is to make what peff@ originally suggested, i.e.

    If we do go with the "print it out and let the caller do their own
    checks" strategy, I think I'd prefer rather than "--show-tagname" to
    just respect the "--format" we use for tag-listing. That would let you
    do:
      git tag -v --format='%(tag)%n%(tagger)'
    or similar. In fact you can already do that with a separate step (modulo
    %n, which we do not seem to understand here)...
work.
Thanks.
Previous: Santiago TorresNext: Michael J Gruber
Message 16 of 21 in “verify-tag: add --check-name flag”
  1. verify-tag: add --check-name flagsantiago@nyu.edu, Jun 7, 2016
  2. Junio C HamanoJun 7, 2016
  3. Jeff KingJun 7, 2016
  4. Santiago TorresJun 7, 2016
  5. Junio C HamanoJun 7, 2016
  6. Jeff KingJun 7, 2016
  7. Junio C HamanoJun 7, 2016
  8. Jeff KingJun 7, 2016
  9. Junio C HamanoJun 7, 2016
  10. Jeff KingJun 7, 2016
  11. Santiago TorresJun 7, 2016
  12. Junio C HamanoJun 7, 2016
  13. Jeff KingJun 7, 2016
  14. Junio C HamanoJun 7, 2016
  15. Santiago TorresJun 8, 2016
  16. Junio C HamanoJun 8, 2016
  17. Michael J GruberJun 9, 2016
  18. Santiago TorresJun 7, 2016
  19. Jeff KingJun 7, 2016
  20. Santiago TorresJun 7, 2016
  21. Jeff KingJun 7, 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.