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

Re: git fetch slow as molasses due to tag downloading

From
Junio C Hamano <junkio@cox.net>
Date
Dec 15, 2006, 21:55 UTC
Message-ID
<7vtzzwn7su.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<Pine.LNX.4.63.0612141701440.3635@wbgn013.biozentrum.uni-wuerzburg.de>
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> IMHO this should be solved as a filter: "git-show-ref --stdin 
> --show-invalid". Thus, git does not have to traverse _every_ ref for 
> _every_ incoming tag.

That sounds like a too specialized hack to me. We should first speed up the general "--verify $ref" case; as you corrected me earlier it still has a useless loop.

If it is still too slow (which I suspect it could be the case, with fork+exec overhead), we should _also_ pursue the filter approach, but even then I think "filter out the valid ones" is a specialized hack, if you mean "show only the invalid one's names" by --show-invalid.

It would make sense to do
        $ git show-ref --show-invalid v1.0.0 v2.6.18
        f665776185ad074b236c00751d666da7d1977dbe refs/tags/v1.0.0
        - refs/tags/v2.6.18
(and its equivalent to take refs from --stdin) though.
Previous: Jakub NarebskiNext: Jakub Narebski
Message 4 of 5 in “git fetch slow as molasses due to tag downloading”
  1. Han-Wen NienhuysDec 14, 2006
  2. Johannes SchindelinDec 14, 2006
  3. Jakub NarebskiDec 15, 2006
  4. Junio C HamanoDec 15, 2006
  5. Jakub NarebskiDec 15, 2006

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.