Re: FAQ about global revisions

Isak Johnsson <isak@hypergene.com> writes:

> If I've got it right, then I'm supposed to put different branches and
> major versions in different directories in the same repository. If that

How you manage 'branches' is up to you. I don't like the /branches
that the svn repository has. I'm managing my repository so that
each project has at least a 'current' directory, analogous to cvs
HEAD. Releases are copied to /releases/foo/foo-version. 'Branches'
or 'tags' are created as needed along-side 'current'.

> I can't count on the
> revision number to know when it's time to rebuild a branch? Nor can I

I don't understand what you mean here.

> correlate bug reports by their revision numbers even if the source is
> identical.

Nor here.

> If the revision number really is repository wide then I'd like to use
> several repositories instead. I tried, but I couldn't get "svn copy URL1

If you do that, you're not going to be able to share code between
projects. For example, we have buildtools, doctools, and portability
modules shared between all our projects.

FWIW, i *like* global revision numbers and can't fathom why so many
people dislike or misunderstand them :-/.

--
Eric Gillespie <*> epg@pretzelnet.org

Build a fire for a man, and he'll be warm for a day. Set a man on
fire, and he'll be warm for the rest of his life. -Terry Pratchett

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jul 15 21:13:12 2002