On Fri, 2009-11-27 at 15:40 +0530, Senthil Kumaran S wrote: > Hi, > > Bhuvaneswaran A wrote: > > Did we discuss about correcting old revisions pointing to svn.collab.net > > repository referenced in log messages? Like this one: > > $ svn log -r r880575 > > This is my first attempt at ctypes-python bindings for subversion :) The > attached script will do the above. I plan to run this script on -r 836401:HEAD > over https://svn.apache.org/repos/asf/subversion/trunk around "15:30:00 > Saturday November 28, 2009 in UTC"
2 things: a) I don't know if the new revisions are sequential. The difference between last revision in the import (r880588) and HEAD (r836420) is 44168. It does not match with the last revision (r40515) committed in svn.collab.net repository. IOW, I don't think we are sure that no other commits were happening in ASF repository while subversion was imported. AFAIK, commits to other Apache projects were not restricted while Subversion repository was imported. However, can you explain how did you arrive at revision r840074 as the starting point? b) If we decide that we should fix those revisions and while we run the script to fix, we should disable post-revprop-change script to avoid sending 1000s of prop change emails to commits@ list. -- Bhuvaneswaran A CollabNet Software P Ltd. | www.collab.net
signature.asc
Description: This is a digitally signed message part
