On Wed, Aug 12, 2009 at 11:50:15AM +0200, Peter Herth wrote:
> Hi John,
> I cannot say anything about the svn version you are using, but I encountered
> such a data loss once with CVS and identified the developer in my case as the
> culprit. The problem was, that the corresponding person was moving the file
> around on his computer. So he did updates from the repository, and
> then overwrote
> the file with "his" version, and such killing all edits by others not
> contained in "his"
> version and then committed it. The same behavior would happen, if you
> have unsaved
> modifications of a file while updating, and then saving the file... So
> you should make
> sure that this is not an user issue.
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.
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.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-08-12 12:02:23 CEST