Here is an example of the VSS action. Note that the file in the svn
repository was created with version 1, and then the second revision of
that file in svn uses the vss version 7, as version 7 was checked-in
after the 05/04/01 date.
$ grep build.h _vss2svn/datachache.VssAction.tmp.txt
3 HCECAAAA LWIAAAAA 1 ADD
/Project/Source/build.h 2 0 \N
4056 \N LWIAAAAA 7 COMMIT
/Project/Source/build.h 2 0 \N
4324 \N LWIAAAAA 8 COMMIT
/Project/Source/build.h 2 0 \N
6510 HCECAAAA IANCAAAA 9 BRANCH
/Project/Source/build.h 2 0 \N
16384 \N IANCAAAA 10 COMMIT
/Project/Source/build.h 2 0 \N
Ok, once you know the scenario, it is easy to fix: Here is the pseudo
VSS code
ss create $/project1
ss add $/project1/file.txt
ss commit $/project1/file.txt
ss commit $/project1/file.txt
ss create $/project2
ss share $/project1/file.txt $/project2/file.txt
ss destroy $/project1
ss commit $/project2/file.txt
ss commit $/project2/file.txt
The old code reported:
>0 AAAAAAAA 1 ADD / 1 0 \N
>1 AAAAAAAA DAAAAAAA 1 ADD /project2/ 1 0 \N
>2 DAAAAAAA CAAAAAAA 1 ADD /project2/file.txt 2
0 \N
>3 \N CAAAAAAA 4 COMMIT /project2/file.txt 2 0 \N
>4 \N CAAAAAAA 5 COMMIT /project2/file.txt 2 0 \N
Please see the "1" in the third line.
The modified code will now generate:
>0 AAAAAAAA 1 ADD / 1 0 \N
>1 AAAAAAAA DAAAAAAA 1 ADD /project2/ 1 0 \N
>2 DAAAAAAA CAAAAAAA 3 ADD /project2/file.txt 2
0 \N
>3 \N CAAAAAAA 4 COMMIT /project2/file.txt 2 0 \N
>4 \N CAAAAAAA 5 COMMIT /project2/file.txt 2 0 \N
Note the "3" in the third line.
Thank you, for looking up this issue.
Dirk
_______________________________________________
vss2svn-users mailing list
Project homepage:
http://www.pumacode.org/projects/vss2svn/
Subscribe/Unsubscribe/Admin:
http://lists.pumacode.org/mailman/listinfo/vss2svn-users-lists.pumacode.org
Mailing list web interface (with searchable archives):
http://dir.gmane.org/gmane.comp.version-control.subversion.vss2svn.user
