Dirk wrote:
initial code checked in, but there is a problem with binary files.
If a binary file is found, the svn:mine-type is set on every change
of the file. Setting a property, without specifying all other
properties will delete all other properties again. I have to
evaluate this further,but for the time being, other types of
properties seem to work.
What if we only set svn:mime-type on adds also? Will that then leave
the others alone, or do all properties need to be set each time?
changing properties in the dumpfile for a file for a specific revision
works like changing the file content itslef: You change the full set
of properties. No delta records or whatever. I was first fouled by the
our code, that remitted an empty propset for any checkin. I was
wondering, why my properties only existed on the first revision, but
disappeared in the second.
But have you tried whether it's possible to leave the propset off
completely for a checkin? I would be willing to bet in that case that
the previous properties will remain intact. So if there are no new
properties to add, then we should not be passing any properties at all.
That is not the same as having an empty propset.
Really, I can't think of a situation where we should be setting any
properties during a conversion at any time other than when we are adding
a file (plus the derivatives of add, e.g. move, restore, etc.)
_______________________________________________
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
