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

Re: Trouble With Dates

From: Ryan Schmidt <subversion-2007b_at_ryandesign.com>
Date: 2007-05-05 01:56:33 CEST

On May 4, 2007, at 11:43, Hilco Wijbenga wrote:

>> Do you mean, you imported your CVS repository into your existing
>> Subversion repository? Or was the Subversion repository empty when
>> you imported into it?
> Yep, into an existing repository.
>> If there was already something in the Subversion repository, then
>> that means that all your revisions proceed chronologically to the
>> point when you imported your CVS repository, at which point, time
>> goes backward, then forward again. This messes up the ability of
>> Subversion to identify revisions by date. And there isn't really a
>> solution. You can use the date feature to find revisions created from
>> now on, but not earlier revisions (reliably).
> Would it be possible to dump the various projects (there's 3 + the new
> one) and somehow rearrange the commits and load it back into a (clean)
> repository?
> Does the dump file store references to revision numbers? Would that
> pretty much prevent me from "fixing" the revision/date links?

There is reposmerge.py:


I don't know if it would work for this situation. (I don't know if it
will work properly with a dumpfile where the revisions are not
already in chronological order.)

If it does work, then the only remaining problem would be if you have
revision numbers recorded in your log messages, because they won't
necessarily be the same anymore after the merged load, and also if
you have any external definitions to specific revision numbers the
same thing would apply.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat May 5 01:58:17 2007

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.