Taner Diler wrote:
> After migrating, I controlled projects in svn. I realized that the
> version order of migrated file was not equal to order in vss:
>
> version date
> 10 11.11.2004 10:16 --> in vss version,
> 15.06.2003
> 9 11.11.2004 10:15 --> in vss version,
> 14.06.2003
> 8 11.11.2004 10:14 --> in vss version,
> 10.05.2003
> 7 11.11.2004 10:13 --> in vss version,
> 01.02.2003
> 6 11.11.2004 10:12 --> in vss version,
> 28.01.2003
> ....
> 2 11.11.2004 10:11 --> in vss version,
> 10.01.2002
> 1 11.11.2004 10:10 --> in vss version,
> 10.01.2002
vss2svn builds a chronological "timeline" of all VSS revisions and uses
that to drive the commits to Subversion. I can't really think of a good
way to fix your problem, unless you can figure out how to hack the VSS
database. Unfortunately, the program can't go off revision numbers alone
because there are no repository-wide version numbers like Subversion
has, so it wouldn't know what order to commit individual files in.
I am copying this to the vss2svn mailing list, which is a completely
separate project from Subversion. Please redirect any further discussion
to that list.
toby
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Nov 29 04:09:24 2004