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

RE: Re: I, too, miss tags.

From: Dale Strickler <DaleStrickler_at_DirecWay.com>
Date: 2006-02-27 21:42:45 CET

At 10:45 2006/02/27 -0500, Rob van Oostrum wrote:
I would change Robs Example like this

> /trunk
> /branches
> /project1/RobsWork/File1.c
> /project2
> /project3
>And I have a property at / saying r100:VERSION_1_0

Now Version_1_0 refers to two version of File1.c in the same
project. You need to remember that in SVN revision numbers are NOT a
revision of a file. They are a revisions of the WHOLE archive at a
single point of transaction, like a commit. All of the other systems
associate a revision number with a file. So there is rev. 10 or
file1.c and rev. 10 of File2.c and there is NOT correlation between
rev. 10 and rev. 10. Thus a tag gives you that correlation,
eventually. In those systems you often assign a Version number to
rev. 10 file1.c and rev 10 file2.c then tag that Version then tag the
Version. (Very simple!) SVN, thankfully, turns this on it's head
and says that when you do something with rev. 10 you are doing
something with a specific transactional state of ALL the files in the
repository. Even if they are the same file being archived by
different people on different branches. Thus, also thankfully, I
have to almost never think about revision numbers or assigning them
to version or assigning them to tags. When I have a milestone point,
the code runs, I do a quick, cheap, labeling to of the code to
/tag/Project1/running_copy. Then I am done!! No though about
numbers. No need to cross correlate Revisions into Versions. No
need to assign anything. Just a name in my hierarchical name
structure that uses a directory metaphor! GREAT! . When I what that
version I just extract it a working directory or do differences to
that 'tagged' metaphorical "file set."

For you folks that feel that old style tags gain something I don't
think you fully realize how different revision numbers are in SVN
than in any of the other tools. There is only ONE number for any
state of the repository! Not dozens that need cross correlation.

I would freely encourage you self-proclaimed "tag supports" to build
a wrapper on SVN but I sure will be disappointed of any of you get
this IMHO 'backwards' complexity, IMHO polluting the code base,
interface, and documentation; indeed I would see that as a bad day in
SVN's history!

SVN's model is great! It is simple. (Not need to try and get a
newbie to keep the terms Revision and Version straight!) And I like
not have the old, out outdated, non-hierarchical approach to tags
gone! Good riddance!

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Feb 27 22:19:35 2006

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