Bruce Wilson wrote:
Nathan Kidd wrote:
Bruce Wilson wrote:
* Edited the dumpfile to make the developer names consistent. (We
used first name, then employee number, then
first-initial-last-name at various times.) Changing the "length"
entry right before each developer name would have been trivial in
the same search-and-replace.
With only 2,900 revisions, an after-migration 'svn propset' would
actually be easier, IMO. Remember author names are revision
properties, and not versioned, so your history won't be full of 2,900
"author changed" revisions.
Hmm, that sounds interesting. The tricky thing would seem to be
identifying which revs need to be updated, right? I could grep (a copy
of...) the revprops folder for clues I suppose. Know of any scripts or
recipes for this?
Roughly:
for rev in 1 .. 2900:
author = svn propget svn:author --revprop svn://repo/eod -r$rev
if author == "foo":
author = "bar"
svn propset svn:author $author --revprop svn://repo/eod -r$rev
But you've got to have enabled (an at least empty) prerevprop hook
script first (check the svn book).
-Nathan
_______________________________________________
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
