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

Re: [PATCH v2 3/3] Teach git-fetch to exploit server side automatic tag following

From
Shawn O. Pearce <spearce@spearce.org>
Date
Mar 5, 2008, 05:56 UTC
Message-ID
<20080305055659.GD8410@spearce.org>
In-Reply-To
<alpine.LSU.1.00.0803041512040.22527@racer.site>
Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> just two comments from me for this patch series:
> 
> - it's a beaut, and
Thanks.
 
> - should followtags not be the default?
No.  Absolutely not.

The client may not want tag objects from this remote. It might not want those tags for all sorts of reasons. Maybe they are doing a one-shot pull. Maybe they don't trust this remote. Maybe they trust this remote but this remote is famous for 192M tags containing PDFs of photo images of build logs printed out on paper, then photographed on a wood table and finally scanned in at 600 dpi.

So it should only be enabled *if* we were willing to open a second connection to this remote to followtags from it. And that's not a change from prior behavior either, its just faster.

-- 
Shawn.
Previous: Johannes SchindelinNext: Johannes Schindelin
Message 3 of 5 in “Teach git-fetch to exploit server side automatic tag following”
  1. 3/3 Teach git-fetch to exploit server side automatic tag followingShawn O. Pearce, Mar 4, 2008
  2. Johannes SchindelinMar 4, 2008
  3. Shawn O. PearceMar 5, 2008
  4. Johannes SchindelinMar 5, 2008
  5. Shawn O. PearceMar 6, 2008

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.