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

Re: Merging 50+ repositories into one

From: Ulrich Eckhardt <eckhardt_at_satorlaser.com>
Date: 2004-11-01 10:33:30 CET

Ross Mark wrote:
> We are now considering merging all of the repositories into one so that
> tracking versions of software for a release would be a lot simpler. We
> know we have to modify the dump files to fix path names to match the new
> repository layout but we are wondering what else we should be aware of?
> For example will the commit dates/times change when loaded into the new
> rep? We make use of the use-commit-times setting for some of the checkouts.

- you should not load two separate dumpfiles as this would lead to
non-contiguous date/time values in the resulting repository
- dumpfilter can modify the paths for you

> Given a lot of our comments about copys and merges make references to
> numeric versions we are considering writing a filter that combine all
> rev 1 for each repository and loading them all in one transaction. Then
> filter all rev 2 for each repository and loading them together that way
> revX of the big repository was the same as revX of the original. The log
> messages would have to concatenated together, authors merged into a list
> and only one of the date stamps could be used. Apart from those problems
> is it a reasonable idea?

I'm working on a tool that reads two dumpfiles, and writes out their revisions
in the order of their commit time, which is the better approach for me. Since
you rely on revisions numbers for internal bookkeeping, this will screw you



To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Nov 1 10:34:19 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.