Re: ambiguous refname
- From: Behdad Esfahbod <behdad behdad org>
- To: Owen Taylor <otaylor redhat com>
- Cc: gnome-infrastructure <gnome-infrastructure gnome org>
- Subject: Re: ambiguous refname
- Date: Sun, 19 Apr 2009 20:02:03 -0400
On 04/19/2009 05:26 PM, Owen Taylor wrote:
On Sun, 2009-04-19 at 16:21 -0500, Shaun McCance wrote:
On Sun, 2009-04-19 at 15:38 -0500, Shaun McCance wrote:
Every time I push gnome-doc-utils changes, to git.gnome.org,
I get this:
error: refname 'GNOME_DOC_UTILS_0_4_3' is ambiguous
It isn't fatal, but I certainly don't want to look at it
for the rest of time. Any ideas what the problem is?
All right, apparently there is both a branch and a tag
named GNOME_DOC_UTILS_0_4_3. I remember now that I'd
accidentally tagged by copying to branches for 0.4.3.
I then moved that to tags to fix it.
So, what's the recommended branch and tag naming scheme going forward?
For cairo, fontconfig, pango, etc we've been using the release number as
branch name and tag name. That is, "1.24.0" is a tag name, "1.24" is the
branch name.
Do we want to move to this simpler scheme, or stay with CVS-style PANGO_1_24_0
vs pango-1-24?
I know I can delete a branch with
I thought deleting tags and branches is prohibited?
behdad
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]