Hi,
this is one of my favorite wishes also ;-)
In my repository I have a branch creation, executed with the exact
above SS command line, that results in no less than 141 svn
revisions !
This is interesting, normally the code can do "folder creations" and
"copies" in one go. So we should have a look here in depth. I'm
wondering, why the comment is missing on the copy. Is it also missing in
the share node from PhysicalAction? I have a lot of places like this,
and they all work fine, but I think I also never use comments, when
doing these kind of actions. Need to try.
Interestingly I have another branch point where no comment was
supplied : vss2svn manages to squeeze it into only 2 svn revisions,
though it is not clear why everything did not fit in a single revision.
I expect, that you have a file that is shared within your project, so
it will end up to be copied two times. The current "revision break"
detection logic will detect, that there was already an operation on the
first share and will force a revision break on the second. I already
tried to solve this, but this is very complex, since the revision
detection logic is at the wrong place in the code. It comes before the
ActionHandler and here we do not have enough information about the real
activity.
Still, this is an awful lot of activity for something that could
have been represented as a single
svn cp /MainProject /Branches/MyFirstBranch -Mcomment
Yes, this would be wonderful. I also thought about this already and
dismissed the idea due to complexity. And also due to lack of time ;-)
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
