2011/5/12 Dave Tingling <dave.tingl...@infotechfl.com>: > Thanks for those tips Konstantin. > > There are about 16 developers. Is there anything I can look at on the server > side to determine whether such bad directory copy/moves have been done, and > perhaps by whom? >
When developer B notices "Frankenstein" file appearing in his working copy he should 1. Look at the history of this file to find who committed it. That is "svn log --limit 3" command. (Or with limit of 1, only recent entries do matter). (Or using TortoiseSVN > Log command in its menu). 2. From the history find who and when committed the file. Let's say it was developer A. 3. Go to A and ask what changes were committed and call "svn info" on that file in A's working copy. (Or using Windows Explorer > File Properties > look at "Subversion" tab, as I wrote before). Pay attention to the file's path in repository. In TortoiseSVN there is "Change for modifications" dialog that I think should show if anything is wrong with files hierarchy in the working copy. >> On the server: what protocol you are using to access the repository and >> commit the files? > > HTTPS...I'm not sure what mechanisms happen "within" or "lower than" that. > Is this a helpful answer? If you need more info, please let me know how I > can find it out. I personally am a facilitator for researching this issue, > I'm not an admin. This is good. HTTPS passes proxies safely and unchanged. One more suggestion: you might consider about installing a post-commit hook at the repository. Tasks that can be performed by such a hook: a) make a dump of the recent commit, b) send a copy of commit diff to an e-mail address. etc. Best regards, Konstantin Kolinko
