At 9/16/2005 10:35 AM, Joshua Varner wrote:
>On 9/15/05, Dale Hirt <dale@sbcltd.com> wrote:
>[snip]
> > 4. Load old repositories using --parent-dir arg
> > svnadmin load new-repos --parent-dir oldrepo1dir < oldrepo1.load
> > svnadmin load new-repos --parent-dir oldrepo2dir < oldrepo2.load
> > svnadmin load new-repos --parent-dir oldrepo3dir < oldrepo3.load
> >
>
>Assuming all three repositories have 100 revs and were
>created on Jan 1 and the dump files are from July 1,
>then the new repository will have dates like this:
>
>Jan 1 ---> July 1 Jan1 ---> July1 Jan1 --> July1
>rev 1 ---> rev 100 rev101 --> rev200 rev 201 --> rev 300
>from repoA from repoB from repoC
>
>The date based checkouts use a binary search, I believe,
>to find the right date, but since the revisions from the three
>separate repositories are only ordered in their own dumpfile
>the resulting repository will not be.
>
>This breaks binary searching on date. If you're not doing
>that, then no big deal, all of the information is present in
>the repository.
Ok, good info.
Will per-file history analysis commands/scenarios (not sure what all they
are--I'm viewing this from a "higher" level and as of yet are not familiar
with all Subversion details) still work?
Also, will binary-date searches beyond July 1 (in the above example) still
work for the new "super" respository?
Additionally: would anyone have any script examples for how to interleave
the dates and revs of the resulting, "super" repository?
-Matt
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Sep 16 19:00:01 2005