From: Junio C Hamano <gitster@pobox.com>
To: "Jon Smirl" <jonsmirl@gmail.com>
Cc: "Junio C Hamano" <gitster@pobox.com>,
"Git Mailing List" <git@vger.kernel.org>
Subject: Re: syntax for checking out specific tag on a remote
Date: Sat, 11 Aug 2007 19:01:28 -0700 [thread overview]
Message-ID: <7vmywxjytj.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <9e4733910708111850v6e9669c3i536fba49f63d0f10@mail.gmail.com> (Jon Smirl's message of "Sat, 11 Aug 2007 21:50:10 -0400")
"Jon Smirl" <jonsmirl@gmail.com> writes:
> 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/*
prev parent reply other threads:[~2007-08-12 2:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-12 1:33 syntax for checking out specific tag on a remote Jon Smirl
2007-08-12 1:41 ` Junio C Hamano
2007-08-12 1:50 ` Jon Smirl
2007-08-12 1:57 ` Jon Smirl
2007-08-12 2:01 ` Junio C Hamano [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vmywxjytj.fsf@assigned-by-dhcp.cox.net \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jonsmirl@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox