There is a script to do this: http://svn.collab.net/viewvc/svn/trunk/contrib/client-side/svn_apply_autoprops.py?view=log
Also there is an auto-props setting when you convert using vss2svn, which will set the properties retroactively over all of the history. If you have migrated but haven't gone live yet, you could use that functionality.
Jason Jon Hardcastle wrote:
Hello, I have an issue that I hoping I get some with from a fellow migrator! I have successfully migrated my repository, and copied over the latest version of all files so it is current and all gaps 'plugged' But now I have an issue. I have promised that all non-source/plain-text files will sport the 'needs-lock' property. i can not for the life of me work out how I can apply this across the entire repository but only to certain extensions of files.. Can anyone help? Rather annoyingly I have set up auto-props but that only works on new files.. it doesn't set it on existing files. Please any pointers gratefully received! ----------------------- N: Jon Hardcastle E: [EMAIL PROTECTED] 'The writing is on the wall...' ----------------------- _______________________________________________ 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
_______________________________________________ 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
