You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Matt England <me...@mengland.net> on 2005/09/30 12:59:20 UTC
How can I run a "binary search based upon date"?
How can I run a "binary search based upon date" as described by Josh below
to test Dale's RepoMerge.py script (as seen here:
http://www.thehirts.net/blog/?page_id=24 ) to make sure things are working?
Sorry if I'm ignorant; I admin Subversion, but I don't use it in a detailed
fashion that much up until now--my developers do more of that.
-Matt
>Date: Fri, 16 Sep 2005 10:35:26 -0500
>From: Joshua Varner <jl...@gmail.com>
>Content-Type: text/plain; charset=ISO-8859-1
>Subject: Saving history when converting multiple repos into one?
>
>On 9/16/05, Dale Hirt <da...@sbcltd.com> wrote:
> > In what sense would it break data-related searches, Josh?
> >
> > It wouldn't be too hard to whip up a script though, to interleave
> various revisions and repos.
> >
>[snip]
>
>On 9/15/05, Dale Hirt <da...@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.
>
>Josh
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: How can I run a "binary search based upon date"?
Posted by Matt England <me...@mengland.net>.
My 'svn log' commands show a history of the dates/revisions of the 2 input
repositories interleaved (the way I would expect it) with each other with a
sequenced list of the revisions of the resulting, merged repositories.
Is this is a test of what I see below? Does it validate (or at least prove
for this test) a working RepoMerge.py?
Or do I need to run some other test?
-Matt
At 9/30/2005 07:59 AM, Matt England wrote:
>How can I run a "binary search based upon date" as described by Josh below
>to test Dale's RepoMerge.py script (as seen here:
>http://www.thehirts.net/blog/?page_id=24 ) to make sure things are working?
>
>Sorry if I'm ignorant; I admin Subversion, but I don't use it in a
>detailed fashion that much up until now--my developers do more of that.
>
>-Matt
>
>
>>Date: Fri, 16 Sep 2005 10:35:26 -0500
>>From: Joshua Varner <jl...@gmail.com>
>>Content-Type: text/plain; charset=ISO-8859-1
>>Subject: Saving history when converting multiple repos into one?
>>
>>On 9/16/05, Dale Hirt <da...@sbcltd.com> wrote:
>> > In what sense would it break data-related searches, Josh?
>> >
>> > It wouldn't be too hard to whip up a script though, to interleave
>> various revisions and repos.
>> >
>>[snip]
>>
>>On 9/15/05, Dale Hirt <da...@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.
>>
>>Josh
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
>For additional commands, e-mail: users-help@subversion.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org