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

RE: Similating "label" feature in Subversion?

From: Jason Winnebeck <jpwasp_at_rit.edu>
Date: 2007-08-28 17:15:28 CEST

-----Original Message-----
From: Bicking, David (HHoldings, IT)
[mailto:David.Bicking@thehartford.com]

4. We cannot look at the history of a file (in a codeline) and see which
labels it received, and do a compare between labels. I am unsure how we
could get the same result in Subversion w/o much manual work...
-----------------

This is possible is some circumstances if you reverse your viewpoint by
resolving by tag and then file rather than file then tag. In a system
like SourceSafe, typically we make labels based on release. Then when
you view file history you can see the labels to find out which version
of the file was in what version.

In subversion, to make releases we make a tag. But now you have a file
dir/xyz.c in your code, and you want to see changes made in xyz.c
between version 1.0 and version 2.0. So, you find the file xyz.c in
tags/1.0 and tags/2.0, and there you can do the differences with 'svn
diff'

This works as well as history-between-labels if you typically tag your
whole project at a time (which is typical with a release model). It
doesn't allow you to easily simulate labels on a single file in time,
and it doesn't work well when the file's location changed between
releases, since you'll have to search manually. So, my advice is based
mostly on the fact that when people want to compare labels what they
really want to do is compare between product releases, and the typical
way of doing this is easily done in SVN.

Jason

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Aug 28 17:13:00 2007

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.