Clean-up command overwriting uncommited files

From: Nick Flack <nick.flack_at_pi-shurlok.com>
Date: Tue, 13 Jan 2009 11:43:21 -0000

I am finding that users are losing work due to the operation of the
cleanup command. The process that is repeatable is as follows:

1. lock a document in my WC

2. open the doc in word, edit it, save it BUT keep it open.

3. attempt to do an SVN update on the directory (this "fails" as I have
got the doc open)

4. add some more text to the document, save it and close it

5. try to commit - this fails saying it is locked, do a cleanup

6. do a SVN cleanup (as suggested) on the directory - this says it has
worked

7. open at the document again - it has not got the changes done in step
4 !!

I am assuming it is using copies it has stored in the .svn driectories
when it does a cleanup...

What would be useful in this instance is to have the cleanup command
issue a warning message before it attempts to recover changed files.

Nick Flack

IT Manager

Pi SHURLOK LTD

A Control Instruments Company

Telephone: +44 (0)1223 441434 / 203447 (direct)

Fax: +44 (0)1223 203999

Mobile: +44 (0)7795 458934

Email: nick.flack_at_pi-shurlok.com <mailto:nick.flack_at_pi-shurlok.com>

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-01-13 14:28:18 CET