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

Strange behaviour of --tags when adding remotes

From
TSTimo Schmiade <timo.schmiade@gmx.de>
Date
Apr 16, 2011, 10:50 UTC
Message-ID
<20110416105017.GA2887@Discworld>
Hi all,

I just stumbled upon what I think is a bit of a strange behaviour when using "git remote add" with the --tags option. The remote I added was fetch'able after the command (it was added to .git/config), but there was no remote tracking branch set up for it (i.e. the .git/refs/remotes/<shortname> directory didn't exist).

Only after removing the "tagopt = --tags" option from .git/config was it that "git fetch <shortname>" created a remote tracking branch for the remote.

After double-checking the "man git-fetch", I still think this behaviour is quite confusing, so I wanted to inform you about this.

Kind regards,
Timo
Message 1 of 1 in “Strange behaviour of --tags when adding remotes”
  1. Timo SchmiadeApr 16, 2011

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.