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

Re: Unclear: CVS and Subversion repository difference.

From: Ryan Schmidt <subversion-2005_at_ryandesign.com>
Date: 2005-06-18 21:11:58 CEST

On 18.06.2005, at 14:17, Saulius Grazulis wrote:

> On Friday 17 June 2005 21:54, Ben Collins-Sussman wrote:
>
>> "I have revision 1200 of the svn client!"
>> Revision 1200 of what branch or path? Do you have (r1200, /trunk)?
>> Or perhaps (r1200, /branches/1.2.x)? Those are two completely
>> different things. If somebody asks me, "so, does that mean I have
>> the bug fixed by r1153?", there's no way for me to know.
>
> Probably thats why many Suvversion users (including me) would like
> to be able
> to assign symbolic names to revisions (VER-1.2.3 == r12345) and
> maybe spare
> the tags/ directory ;). And branches would be, well, branches -- some
> independent (maybe very experimental) development of the project.

Oh, no, please, let's not start *that* discussion again. We just had
it a short while ago, on this list, to the tune of several hundred
messages, and leading me to the inescapable conclusion that assigning
symbolic names to revisions just doesn't get you anywhere. As Ben has
been repeatedly pointing out, a revision number alone tells you
nothing. If my repository has three directories at the root level --
foo, bar, and baz, representing three separate projects -- then the
same point in time -- the same revision 12345 -- represents different
things in those three directories. The current version of foo might
be version 1.1, of bar 2.5, and of baz 3.1.4. Thus in order to get
meaning, you need a revision *and* a path. Assigning a label like
"VER-1.2.3" to revision 12345 is completely useless since a revision
number is global to the repository but not all three projects in my
repository are at the same version.

Possibly you'll tell me that you create separate repositories for
separate projects. Fantastic; I don't. I very much value that I have
all my projects in one repository and intend to keep it that way, and
I appreciate that the Subversion team works to create general
solutions that can be used by anyone, not specialized solutions only
applicable to people doing things one particular way.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Jun 18 21:13:54 2005

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