[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 22:42:32 CET

> -----Original Message-----
> From: Saulius Grazulis [mailto:grazulis@ibt.lt]
> Sent: Monday, February 27, 2006 5:11 AM
> To: users@subversion.tigris.org
> Subject: Re: I, too, miss tags.
> On Monday 27 February 2006 18:59, Rob van Oostrum wrote:
> > Imagine a repository holding a single product like so:
> >
> > / -> r300 = SOME_TAG
> >         /trunk -> r400 = VERSION_2_1
> >         /branches
> >                 /project1 -> r100 = VERSION_1_0
> >                 /project2
> >                 /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?
> The same way how you find it it the current tags/ dir.
> More specifically, I would go to the project1/ dir (since I suppose you
> are

Trunk and Project1-3 in my example above represent 4 development streams of the same product/application/codebase. The tags represent 3 different releases of the application.

So not knowing specifically where to look, you'd have to start traversing from the root down unless your script is aware of the meaning of the repository layout and already knows it only needs to query direct subdirectories of /branches, as well as /trunk .

Once it does find a tag, where does the checkout begin from? The first directory level the tag appears in? Do you find the location of the tag first, and then run the checkout command separately passing the retrieved URL & tag/revision?

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:58:06 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.