Re: ambiguous refname

On Mon, 2009-04-20 at 23:15 -0400, Behdad Esfahbod wrote:
> On 04/20/2009 11:12 PM, Vincent Untz wrote:
> > Le dimanche 19 avril 2009, à 20:02 -0400, Behdad Esfahbod a écrit :
> >> 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?
> >
> > Why would we change?
> Well, it's so much easier to type "git diff 1.24.0.."...
> Was just wondering, since that's the common practice I've seen in other 
> projects using git.

I think the current scheme for the branches for stable
Gnome series is fine.  For release version tags, though,
I have to admit I'm pretty tired of typing things like
GNOME_DEVEL_DOCS_2_25_1.  Not too bad for yelp, but for
gnome-devel-docs, gnome-doc-utils, and gnome-user-docs,
it's a pain.

> > At least for branches in GNOME modules, keeping gnome-2-26 makes sense
> > since not all modules follow the GNOME version numbers...


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]