On Fri, 2006-08-04 at 21:56, Troy Curtis Jr wrote:
> I am attempting to convert my the RCS repository that we use at work
> over to subversion. I was able to successfully use cvs2svn (with a
> couple of tweaks) and got all of our changes into the shiny new
> subversion repo. The first issue is that it ballooned a ~1GB RCS
> repository to ~2GB, but we can deal with that...especially since it
> took us 12 years or so to get the first 1GB. Also, the HEAD revision
> is 60202, so there are a lot of commits.
>
> The main problem is checkout times, which are sitting at 5.5 minutes
> over LAN.
I have something close to the same scenario with a decade-old CVS
repository and will probably just move over the current HEAD version
for continuing work and keep the old repository around for the
unlikely event that someone wants to go back. However, is this
an artifact of conversion or where everyone is headed with
subversion after a few years as a result of the design decision
to reconstruct from the oldest rev and deltas every time instead
of maintaining the most recent and applying delta's backwards like
rcs/cvs do it?
> All that background to ask this question: Is there a way to tell
> subversion to build a complete revision at some specific point and
> then diff from there on(note that I only care about doing this to the
> trunk, the branches can stay where they are). This way the svnserver
> will only have to go back a relatively few revisions. But we have to
> have the past revisions, so I cannot just start a new repository at
> some arbitrary point. Specifically we need the log messages of all
> those revisions. Exporting the HEAD, then deleting all the files, and
> then importing the exported files would get the fresh copy of the code
> set into a specific rev, but then I would not have the logs and
> previous diffs for all the prior revisions.
Do you need those old log messages all the time or just some
access to them? A quick fix would be to "svnadmin dump" the
recent range you're likely to want and build a new working
repository while keeping the old complete one around for
the times you need it. That also would have the advantage
of making the changing repository that needs frequent backups
much smaller.
--
Les Mikesell
lesmikesell@gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Aug 5 19:50:42 2006