[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: Rob van Oostrum <rob.vanoostrum_at_blastradius.com>
Date: 2006-02-27 17:59:38 CET

> -----Original Message-----
> From: Scott Palmer [mailto:scott.palmer@2connected.org]
> Sent: Monday, February 27, 2006 10:23 AM
> To: users@subversion subversion
> Subject: Re: I, too, miss tags.


> > So when searching for a tag, your wrapper script would have to
> > traverse
> > ALL branches, and somehow figure out how to chose between
> I haven't got the foggiest idea what you are talking about. What I
> proposed would not require any of that.

Imagine a repository holding a single product like so:

/ -> r300 = SOME_TAG
        /trunk -> r400 = VERSION_2_1
                /project1 -> r100 = VERSION_1_0
                /project3 -> r200 = VERSION_2_0

My point was, unless you know exactly where to start looking, how would
you find VERSION_1_0 without starting at / and traverse down the tree?
If you only look in /, /trunk and every top folder underneath /branches,
wouldn't you be forcing that repository layout on every user?

Also, what would the significance of SOME_TAG be?

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Feb 27 19:47:31 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.