# Re: please consider remove those tags named master, which is ambigous with master branch 3 messages from 2008-09-23 to 2008-09-24. Participants: rae l, Alex Riesen, Andreas Ericsson. Thread: https://gitlist.dev/t/15636 ## rae l, 2008-09-23 14:46 Subject: Re: please consider remove those tags named master, which is ambigous with master branch Message-ID: <91b13c310809230746o1c2cb694taebc814bea57c8c5@mail.gmail.com> URL: https://gitlist.dev/e/91b13c310809230746o1c2cb694taebc814bea57c8c5%40mail.gmail.com In-Reply-To: <91b13c310808310948r5e9e825as27bcdf381137e179@mail.gmail.com> ``` To Smurf and Andrew: Did you notice that there's a tag named "master" in the smurf mm-trees.git repo, this would confuse the git and the users, please consider remove the "master" tag, OK? ---------- Forwarded message ---------- From: rae l Date: Mon, Sep 1, 2008 at 12:48 AM Subject: please consider remove those tags named master, which is ambigous with master branch To: Matthias Urlichs please consider remove those tags named master, which is ambigous with master branch http://git.kernel.org/?p=linux/kernel/git/smurf/linux-trees.git;a=tags -- To Git developers: I found that different git subcommand have inconsitent processing about ambiguous refname, git show will take "master" tag first, while git tag -v will take "master" branch first, So what's your suggestion to fix this? Just simple remove ambiguous refnames? Or we can add a feature to allow same refname in different namespaces (tags and branches)? Such as "-b" to refer a branch while "-t" to refer a tag name? Else how to distinguish them? gektop@tux ~/sforge/linux-2.6 0 $ PAGER= git show master warning: refname 'master' is ambiguous. commit 05230bd16821e2ec80321d72e97e7a2b1a07c6f2 Author: Adrian Bunk AuthorDate: Sat Jul 30 00:45:08 2005 +0000 Commit: Matthias Urlichs CommitDate: Mon Aug 1 05:16:36 2005 -0700 sound-oss-sequencer_syms-unexport-reprogram_timer This patch remoes an unneeded EXPORT_SYMBOL. Signed-off-by: Andrew Morton diff --git a/sound/oss/sequencer_syms.c b/sound/oss/sequencer_syms.c index 45edfd7..5d00879 100644 --- a/sound/oss/sequencer_syms.c +++ b/sound/oss/sequencer_syms.c @@ -19,7 +19,6 @@ EXPORT_SYMBOL(sequencer_timer); EXPORT_SYMBOL(sound_timer_init); EXPORT_SYMBOL(sound_timer_interrupt); EXPORT_SYMBOL(sound_timer_syncinterval); -EXPORT_SYMBOL(reprogram_timer); /* Tuning */ gektop@tux ~/sforge/linux-2.6 0 $ git tag -v master error: 05230bd16821e2ec80321d72e97e7a2b1a07c6f2: cannot verify a non-tag object of type commit. error: could not verify the tag 'master' -- Denis Cheng Renquan ``` ## Alex Riesen, 2008-09-24 15:44 Subject: Re: please consider remove those tags named master, which is ambigous with master branch Message-ID: <81b0412b0809240844y42218bedqe0e1eb22c067fcc3@mail.gmail.com> URL: https://gitlist.dev/e/81b0412b0809240844y42218bedqe0e1eb22c067fcc3%40mail.gmail.com In-Reply-To: <91b13c310809230746o1c2cb694taebc814bea57c8c5@mail.gmail.com> ``` 2008/9/23 rae l : > To Git developers: > I found that different git subcommand have inconsitent processing > about ambiguous refname, > > git show will take "master" tag first, > while git tag -v will take "master" branch first, > > So what's your suggestion to fix this? Just simple remove ambiguous refnames? You can use "refs/tags/master" and "refs/heads/master"... ``` ## Andreas Ericsson, 2008-09-24 18:56 Subject: Re: please consider remove those tags named master, which is ambigous with master branch Message-ID: <48DA8D76.1070207@op5.se> URL: https://gitlist.dev/e/48DA8D76.1070207%40op5.se In-Reply-To: <81b0412b0809240844y42218bedqe0e1eb22c067fcc3@mail.gmail.com> ``` Alex Riesen wrote: > 2008/9/23 rae l : >> To Git developers: >> I found that different git subcommand have inconsitent processing >> about ambiguous refname, >> >> git show will take "master" tag first, >> while git tag -v will take "master" branch first, >> >> So what's your suggestion to fix this? Just simple remove ambiguous refnames? > > You can use "refs/tags/master" and "refs/heads/master"... Apart from that.. "git tag -v" taking a branch *at all* is not something we want to happen, as it's supposed to verify the pgp signature of a signed tag. Are you absolutely 100% certain that "git tag -v" tries to verify refs/heads/master as a tag object? -- Andreas Ericsson andreas.ericsson@op5.se OP5 AB www.op5.se Tel: +46 8-230225 Fax: +46 8-230231 ```