"Jon Smirl" [off-list ref] 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.
Hence you would say:
git checkout v2.6.19
to get a detached HEAD at v2.6.19, or if you want to start a
branch from there,
git checkout -b my19 v2.6.19
On 8/11/07, Junio C Hamano [off-list ref] wrote:
"Jon Smirl" [off-list ref] writes:
quoted
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?
Hence you would say:
git checkout v2.6.19
to get a detached HEAD at v2.6.19, or if you want to start a
branch from there,
git checkout -b my19 v2.6.19
--
Jon Smirl
jonsmirl@gmail.com
On 8/11/07, Jon Smirl [off-list ref] wrote:
On 8/11/07, Junio C Hamano [off-list ref] wrote:
quoted
"Jon Smirl" [off-list ref] writes:
quoted
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?
This seems inconsistent to me. Remote heads have their own namespace
but remote tags don't.
--
Jon Smirl
jonsmirl@gmail.com