[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Is label support in future release?

From: Nikki Locke <info_at_trumphurst.com>
Date: 2006-11-20 17:30:05 CET

Phyrefly wrote:
> Nobody's saying that branching should be removed, just that a simpler
> function-set is needed for simpler purposes.
>
> If you need to fix a bug from a prior revision, that is when branching
> is needed, it shouldn't be needed when all you want to do is identify
> a release-point. If you label, rather than tag, to identify a stable
> build, then identifying that point is easy at any point in the future.
> And should you need to branch from it, that function is easy too.
>
> The proposed solution of a copied-to property makes identifying the
> revision you need to look at easy, but it still means having to look
> (quickly) through the rev history to find the rev number with that
> property, and then plug that rev number into other svn commands.
>
> The main advantage of labelling (for basic users) in other source
> control apps is the ability to plug a label name into svn commands
> instead of rev #s. Tagging doesn't allow that, and tweaking the
> tagging functionality, while making the alternative workflows easier,
> doesn't completely solve this.

I speak from a position of some ignorance here, but which subversion
commands will accept a revision number (or, in the proposal, a label) but
will NOT accept a tag in the same place in the command line, to mean the
same thing?

-- 
Nikki Locke, Trumphurst Ltd.      PC & Unix consultancy & programming
http://www.trumphurst.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Nov 20 17:31:01 2006

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.