From: Andreas Ericsson <ae@op5.se>
To: Alex Riesen <raa.lkml@gmail.com>
Cc: rae l <crquan@gmail.com>, Matthias Urlichs <smurf@smurf.noris.de>,
Andrew Morton <akpm@linux-foundation.org>,
git@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: please consider remove those tags named master, which is ambigous with master branch
Date: Wed, 24 Sep 2008 20:56:54 +0200 [thread overview]
Message-ID: <48DA8D76.1070207@op5.se> (raw)
In-Reply-To: <81b0412b0809240844y42218bedqe0e1eb22c067fcc3@mail.gmail.com>
Alex Riesen wrote:
> 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
prev parent reply other threads:[~2008-09-24 19:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <91b13c310808310948r5e9e825as27bcdf381137e179@mail.gmail.com>
2008-09-23 14:46 ` please consider remove those tags named master, which is ambigous with master branch rae l
2008-09-24 15:44 ` Alex Riesen
2008-09-24 18:56 ` Andreas Ericsson [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=48DA8D76.1070207@op5.se \
--to=ae@op5.se \
--cc=akpm@linux-foundation.org \
--cc=crquan@gmail.com \
--cc=git@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=raa.lkml@gmail.com \
--cc=smurf@smurf.noris.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.