git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: please consider remove those tags named master, which is ambigous with master branch

From
Andreas Ericsson <ae@op5.se>
Date
Sep 24, 2008, 18:56 UTC
Message-ID
<48DA8D76.1070207@op5.se>
In-Reply-To
<81b0412b0809240844y42218bedqe0e1eb22c067fcc3@mail.gmail.com>
Alex Riesen wrote:
Show 11 quoted lines
> 2008/9/23 rae l <crquan@gmail.com>:
>> 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
Previous: Alex Riesen
Message 3 of 3 in “Re: please consider remove those tags named master, which is ambigous with master branch”
  1. rae lSep 23, 2008
  2. Alex RiesenSep 24, 2008
  3. Andreas EricssonSep 24, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.