From: Sergey Organov <sorganov@gmail.com>
To: git@vger.kernel.org
Subject: Tags from each remote in a separate "name-space"?
Date: Thu, 28 Feb 2019 08:54:23 +0300 [thread overview]
Message-ID: <87d0ncihkg.fsf@javad.com> (raw)
Hello,
How do I configure git to handle tags from remotes in a manner similar
to branches?
Specifically, I want tag 'tag_name' from remote 'origin' to have local
name 'origin/tag_name', not 'tag_name', as it is by default. For a repo
with a lot of remotes[*] it would allow to keep track of what tag came from
where, as well as prevent name conflicts between tags from different
remotes (and/or local tags).
Fetch-only solution ('fetch', 'pull', and 'remote update' support only)
would do, though push support would be interesting to have as well, so
that, say
$ git push origin/tag_name
works as
$ git push origin origin/tag_name:refs/tags/tag_name
Am I dreaming, or is it already supported?
[*] I ran into it managing Linux kernel sources for different ARM
architectures. Mainstream Linux plus stable Linux plus 2 vendor-specific
remotes plus 3 our local remotes made a mess of various tags in the
repository.
-- Sergey
next reply other threads:[~2019-02-28 6:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-28 5:54 Sergey Organov [this message]
2019-02-28 8:11 ` Tags from each remote in a separate "name-space"? Duy Nguyen
2019-03-01 14:51 ` Sergey Organov
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=87d0ncihkg.fsf@javad.com \
--to=sorganov@gmail.com \
--cc=git@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).