From: Marc Branchaud <marcnarc@xiplink.com>
To: Nathan Gray <n8gray@n8gray.org>
Cc: git@vger.kernel.org
Subject: Re: Why aren't tag refs namespaced?
Date: Thu, 26 Apr 2012 16:06:36 -0400 [thread overview]
Message-ID: <4F99AACC.2050409@xiplink.com> (raw)
In-Reply-To: <CA+7g9Jxc6eaCUR8aVhqKH--sOrvQVrZn+se7wtFJsOiKNjz9Pg@mail.gmail.com>
On 12-04-26 02:40 PM, Nathan Gray wrote:
> Hey guys,
>
> Namespacing works really well for branch refs. I know that
> remotes/origin/master is origin's master branch. I may or may not
> have a master branch, and it may or may not have anything in common
> with origin's. Our repositories are independent, after all, so it
> makes sense that our refs would live in different namespaces.
>
> So why is it that tag refs don't follow this model? Why is my
> "best-commit-ever" tag assumed to be the same as origin's? Given a
> ref in refs/tags it's unclear if the ref is public, private, on origin
> or not on origin. Will pushing my tags create anything new or not?
> Who knows? Compare this to branches, where the same questions are
> easy to answer thanks to namespacing.
There was lengthy, but inconclusive, discussion about this a year ago:
http://thread.gmane.org/gmane.comp.version-control.git/165799/focus=166290
M.
next prev parent reply other threads:[~2012-04-26 20:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-26 18:40 Why aren't tag refs namespaced? Nathan Gray
2012-04-26 19:24 ` Junio C Hamano
2012-04-26 23:33 ` Nathan Gray
2012-04-27 3:26 ` Junio C Hamano
2012-04-26 20:06 ` Marc Branchaud [this message]
2012-04-26 23:34 ` Nathan Gray
[not found] ` <CABURp0okZ=-sq7e0ReUepCOEUC=9r2845wQ6H3HhruRg8Jd6Dg@mail.gmail.com>
2012-04-26 23:48 ` Nathan Gray
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=4F99AACC.2050409@xiplink.com \
--to=marcnarc@xiplink.com \
--cc=git@vger.kernel.org \
--cc=n8gray@n8gray.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).