git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "rae l" <crquan@gmail.com>
To: "Matthias Urlichs" <smurf@smurf.noris.de>
Cc: "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: Tue, 23 Sep 2008 22:46:08 +0800	[thread overview]
Message-ID: <91b13c310809230746o1c2cb694taebc814bea57c8c5@mail.gmail.com> (raw)
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 <crquan@gmail.com>
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 <smurf@smurf.noris.de>

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 <bunk@stusta.de>
AuthorDate: Sat Jul 30 00:45:08 2005 +0000
Commit:     Matthias Urlichs <smurf@hera.kernel.org>
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 <akpm@osdl.org>

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

       reply	other threads:[~2008-09-23 14:47 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 ` rae l [this message]
2008-09-24 15:44   ` please consider remove those tags named master, which is ambigous with master branch Alex Riesen
2008-09-24 18:56     ` Andreas Ericsson

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=91b13c310809230746o1c2cb694taebc814bea57c8c5@mail.gmail.com \
    --to=crquan@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=git@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 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).