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

Re: Repository Layout - One Vs. Many

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: 2004-03-25 17:46:29 CET

"Brian Beaudet" <bbeaudet@efficiencylab.com> writes:

> OK! This is starting to come together in my poor, overworked mind. I'm
> leaning towards one single repository with many projects inside it.
> Each project contains the typical trunk, branches. So for Project1
> under trunk, I'd have all of my typical directories (build, doc,
> install, etc.).
>
> If I decide to branch from there (say for a new version of the same
> Project with specific changes) I'd copy everything from the trunk to a
> branch directory and name that branch something useful.
>
> If I have completed, releasable (or testable) version I'd copy that to
> the tags directory with a useful name that I could track myself. So,
> under tags\ I might have Release 1.0.1 and Release 1.0.2, etc or Testing
> 1.0.1, Testing 1.0.5001, etc. I name these myself and I'd know what's
> next because I'm naming these manually.
>
> Am I close?

Dead close. They don't even have to be manual tag names. No reason
why you couldn't do:

   svn cp url://.../trunk url://.../tags/build-`date --iso-8601`

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Mar 25 17:48:11 2004

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