[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: SVN 1.5.3 and possible data loss

From: Vincent Lefevre <vincent+svn_at_vinc17.org>
Date: Wed, 12 Aug 2009 14:23:57 +0200

On 2009-08-12 11:01:15 +0100, Stefan Sperling wrote:
> Yes. Editors that simply ignore and overwrite concurrent file
> modifications made by other tools (such as Subversion) are no fun.
> So make sure your developers are using editors that handle this
> gracefully, or have them exit their editor before running svn update.

Yes, but this isn't sufficient. I suspect that some users do
the following:
  1. Copy the file somewhere else (e.g. on a USB key).
  2. Do some "off-line" editing. And when they come back:
  3. Do "svn up".
  4. Copy the edited file to the working copy (with "cp").

(Now I wonder whether a Subversion aware "cp" should be provided,
to warn the user against possible damage if the destination is a
versioned file.)

> As an additional safety net, your developers should make a habit
> of looking at the diffs they are about to commit and make sure
> the diff *really* contains only their own modifications. This is
> good practice anyway for additional reasons. For example, there
> may be an unrelated edit in the working copy still lying around
> from last week which might be committed unnoticed. Also, checking
> the diff often makes small errors such as indentation problems more
> easily visible than when looking at the entire file.

I agree!

Vincent Lefèvre <vincent@vinc17.org> - Web: <http://www.vinc17.org/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/>
Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon)
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-08-12 14:24:55 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.