Gert Kello wrote:
[1]
http://subversion.tigris.org/tools_contrib.html#svn_apply_autoprops_py
Good find, that looks like exactly the right tool.
From the description, it does apply those to working folder. It means
that if the file has mime-type application/octet-stream in earlier
revisions, svn diff will probably refuse to work by default on those
revisions.
True, it wouldn't work for earlier versions of the file.
You can see in the Vss2Svn::Dumpfile::Node::set_initial_props()
method[1] that we are already setting the "application/octet-stream"
mime-type if VSS had identified the file as "binary". That function
would probably be a good place to implement the sort of auto-props
functionality you refer to.
The code for actually writing the props to the dumpfile is already in
place; all that needs to be done is parse the auto-props list at some
point in the program (probably Initialize() if it's based of
command-line parameters) and call add_prop() as necessary for each Node.
(To answer your original question, no, I don't think anyone is working
on that issue currently, but it shouldn't be too difficult and doesn't
require much additional knowledge of the rest of the script).
toby
[1]<http://www.pumacode.org/projects/vss2svn/browser/trunk/script/Vss2Svn/Dumpfile/Node.pm#L43>
_______________________________________________
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