Re: Improve tags

From: Nanako Shiraishi <nanako3@lavabit.com>
Date: Mar 26, 2009, 21:53 UTC
Message-ID: <20090327065356.6117@nanako3.lavabit.com>
In-Reply-To: <49CB798B.4090107@gmail.com>

Quoting "Etienne Vallette d'Osia" <dohzya@gmail.com>:

Show 5 quoted lines

> In addition, branches are a way to specify streams,
> not a way to specify an aim for a commit.
> (like in ruby a class is a method container, not a type)
> So branch names are often like next, pu, dev, test, stupid-idea, etc.
> They are totally useless for tracking aims.

Why should that be? 'next' clearly states the aim (it is to serve as an integration testing area for the possible new features for the next release).

Quoting http://article.gmane.org/gmane.comp.version-control.git/113812

 (1) Name your (eh, "my") branch just like you name your function.

     You probably learned in programming 101 course the importance of
     giving a good name to your functions.  The same principle applies.
     When I see kb/checkout-optim branch, I know it is about optimizing
     the checkout command, and it came from Kjetil Barvik.  I can tell
     that jc/maint-1.6.0-read-tree-overlay is about the bugfix to the
     "overlay" feature of read-tree command, and the fix would apply as
     far back as the 1.6.0.X series, not just the current maintenance.

-- 
Nanako Shiraishi
http://ivory.ap.teacup.com/nanako3/