> -----Original Message-----
> From: Marc [mailto:firstname.lastname@example.org]
> Sent: Friday, September 22, 2006 8:07 PM
> To: 'Andy Levy'
> Cc: 'Subversion Users List'
> Subject: RE: Post Commit Working Copy Update - windows
> What are the pitfalls of having "extra" files in the
> development and live
> website directories, that are not under version control? What is the
> likelyhood of a real disaster, and what types of things could cause a
> disaster to occur?
A "problem" is that 'svn update' will not destroy work, so you will need
to audit your workspace.
* If a new version 'foo.java' is checked in, and someone has modified
'foo.java' directly in the workspace, then 'svn update' will not update
foo.java, which means that your workspace is now wrong. This applies to
* If you delete a directory/file, 'svn update' will not delete the
dir/file in the workspace.
Since you cannot 100% guarantee that no one will touch a file in the
workspace, or checkin a file with the same name as a file generated by
the CMS, or prevent folks from deleting files, you will need to audit
your workspace using 'svn status'. Look for M's and D's, to find
modified or deleted files/dirs. Use 'svn revert' to undo the M's so
they correct copy will be loaded by 'svn update'. Deletions are a bit
trickier to process automatically because you need to parse the output
of 'svn update' to notice deletes, which is complicated by the fact that
a 'svn rename' or 'svn mv' does a delete and add.
1. 'svn status'
2. Revert (or save off) any M's
3. 'svn update' > update.log
4. Scan the update.log for deletes and delete the corresponding
workspace file/dir, unless the delete was part of a pair of add & delete
operations from a 'svn ren/mv'.
The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential, proprietary, and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from all computers. GA621
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Mon Sep 25 16:16:24 2006