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

Re: Tags of non-commits

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 24, 2007, 18:49 UTC
Message-ID
<7vwsvkdaz0.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<Pine.LNX.4.64.0708241337560.5774@iabervon.org>
Daniel Barkalow <barkalow@iabervon.org> writes:
> There seems to be an inconsistency between the fetch and tag over whether 
> lightweight tags of non-commits are allowed. Fetch doesn't like them, but 
> tag creates them without any particular fuss.

Is your "fetch does not like them" about the automated following? If you say "git fetch $remote tag $that_tag" there shouldn't be any difference.

And the difference in the automated following behaviour is deliberate. Lightweight ones tend to be private "anchor point" during development (these days we need that less often, thanks to reflogs), and annotated ones, especially the signed kinds are meant for public consumption.

Previous: Daniel BarkalowNext: Daniel Barkalow
Message 2 of 4 in “Tags of non-commits”
  1. Daniel BarkalowAug 24, 2007
  2. Junio C HamanoAug 24, 2007
  3. Daniel BarkalowAug 24, 2007
  4. Junio C HamanoAug 24, 2007

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.