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

revision numbers, and a single repo versus multiple repos?

From: Robert P. J. Day <rpjday_at_mindspring.com>
Date: 2004-12-19 16:59:16 CET

  again, a beginner question, but i have a current project under CVS i
want to move over to svn. i already know that there's too much under
a single CVS repository, and i want to break it into more than one svn
repository (but with each repo representing what you would call
several CVS "modules"). one of the reasons is that, as i read it,
revision numbers are incremented on a per-repo basis.

  now, if only a small part of the repo changes frequently, then of
course the revision number of the entire repo will be constantly
updated even though much of the repo isn't changing at all.

  technically, not a problem, of course. but philosophically, i'm
thinking that it might be nice to have relatively separate "modules"
having their revision numbers being incremented independently. and
this means that, to build my entire project, the build process itself
would have to do multiple checkouts to get all the necessary
components.

  thoughts on this? what's the standard practise in situations like
this? should i care if a repo's revision number changes frequently
even though only a small part of the repo is actually being modified?

rday

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Dec 19 17:02:31 2004

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.