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

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

From
Santiago Torres <santiago@nyu.edu>
Date
Jun 7, 2016, 22:16 UTC
Message-ID
<20160607221621.GG24676@LykOS.localdomain>
In-Reply-To
<20160607221325.GA21166@sigill.intra.peff.net>
On Tue, Jun 07, 2016 at 06:13:25PM -0400, Jeff King wrote:
Show 22 quoted lines
> On Tue, Jun 07, 2016 at 03:11:47PM -0700, Junio C Hamano wrote:
> 
> > On Tue, Jun 7, 2016 at 3:07 PM, Jeff King <peff@peff.net> wrote:
> > >>
> > >> Puzzled.  I didn't even use --format=%(tagname) in the above.
> > >
> > > No, but you used --show-tagname, which does not exist today (and which
> > > IMHO should be implemented as --format). Would --show-tagname take
> > > either a tagname _or_ a sha1? I assume it would not be calling
> > > get_sha1(), as having it find refs/heads/$tag would be silly.
> > 
> > And you do not even want to rely on where refs/tags/* it lives.
> > show-tagname, as I hinted in the first response, was meant to be
> > a short-hand for
> > 
> >        git cat-file tag $tag_object_name | sed -e '/^$/q' -e 's/^tag //p'
> > 
> > so I am still puzzled.
> 
> If you are suggesting that you can do the whole thing today by parsing
> the tag object yourself, then sure, I agree. I thought the point of the
> exercise was to make that less painful for the callers.

This is what I understand so far, it seems all of us are on the same understanding here?

1.- we can do this right now by sed-ing out the tagname, but it might
    not be optimal.
2.- We can, instead, provide a --format flag to git tag -v for the same
    purpose. Which would only print the tag (if the appropriate format
    string is provided)

I still agree with the rest of Peff's comments about this approach. I'm not sure about which approach to take either.

-Santiago.
Previous: Jeff KingNext: Junio C Hamano
Message 11 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.