How do I detect adds, deletes, copies and renames in a working copy after theyve already happened?
You don’t. It’s a bad idea to try. The basic design of the working copy has two rules: (1) edit files as you please, and (2) use a Subversion client to make any tree-changes (add, delete, move, copy). If these rules are followed, the client can sucessfully manage the working copy. If renames or other rearrangements happen outside of Subversion, then the UI has been violated and the working copy might be broken. The client cannot guess what happened. People sometimes run into this problem because they want to make version control “transparent”. They trick users into using a working copy, then have a script run later that tries to guess what happened and run appropriate client commands. Unfortunately, this technique only goes a short distance. ‘svn status’ will show missing items and unversioned items, which the script can then automatically ‘svn rm’ or ‘svn add’. But if a move or copy has happened, you’re out of luck. Even if the script has a foolproof way of detecting these things, ‘sv
Related Questions
- My customer in the UK is requesting copies of all licenses pertaining to them. Can I send a copy of an approved DSP5 overseas?
- PhotoKit Sharpener was correctly installed and working, but now it comes up with a demo dialog, what happened?
- How do I detect adds, deletes, copies and renames in a working copy after theyve already happened?
