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

Re: Tags of non-commits

From
Daniel Barkalow <barkalow@iabervon.org>
Date
Aug 24, 2007, 19:13 UTC
Message-ID
<Pine.LNX.4.64.0708241506300.5774@iabervon.org>
In-Reply-To
<7vwsvkdaz0.fsf@gitster.siamese.dyndns.org>
On Fri, 24 Aug 2007, Junio C Hamano wrote:
Show 15 quoted lines
> 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.
I get a bunch of:
error: Object 0938d5832b4e40e6f440fa5c424c77b70714fb59 is a blob, not a commit

lines. I think it's either in trying to decide whether they should be put in FETCH_HEAD or in trying to determine reachability through them. The server also seems to be unable to tell that I already have the blobs, and sends a pack of all of them each time I pull with tags.

	-Daniel
*This .sig left intentionally blank*
Previous: Junio C HamanoNext: Junio C Hamano
Message 3 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.