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

Re: syntax for checking out specific tag on a remote

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 12, 2007, 02:01 UTC
Message-ID
<7vmywxjytj.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<9e4733910708111850v6e9669c3i536fba49f63d0f10@mail.gmail.com>
"Jon Smirl" <jonsmirl@gmail.com> writes:
Show 13 quoted lines
> On 8/11/07, Junio C Hamano <gitster@pobox.com> wrote:
>> "Jon Smirl" <jonsmirl@gmail.com> writes:
>>
>> > What's the syntax for checking out a specific tag on a remote?
>>
>> This depends on where you stored the tags you obtained from the
>> remote.  By default, "git fetch --tags" would store the tags in
>> a flat namespace; there is no "remote tag" namespace.
>
> I've been storing unrelated trees in the same git db. It never
> occurred to me that there was a single tag name space. So if two of my
> remotes both make a tag TEST then last one fetched will win? Are
> "remote tag" namespaces planned for the future?
There actually is no need to plan anything.

Typically people do not publish "private" tags to require such a layout to differentiate tags from 47 different sources, so we have never talked about this, but you can look into .git/config file in your repository, and adjust [remote "foo"] fetch lines to your specific taste. e.g.

	[remote "a"]
        	fetch = +refs/heads/*:refs/remotes/a/*
                fetch = +refs/tags/*:refs/remote-tags/a/*
	[remote "b"]
        	fetch = +refs/heads/*:refs/remotes/b/*
                fetch = +refs/tags/*:refs/remote-tags/b/*
Previous: Jon Smirl
Message 5 of 5 in “syntax for checking out specific tag on a remote”
  1. Jon SmirlAug 12, 2007
  2. Junio C HamanoAug 12, 2007
  3. Jon SmirlAug 12, 2007
  4. Jon SmirlAug 12, 2007
  5. Junio C HamanoAug 12, 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.