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

Unnoticed conflicts when moving or deleting

From: Ingo Adler <dev_at_synacon.ch>
Date: 2005-04-16 09:42:46 CEST


I have a big problem with svn - as a former CVS user and in general.

Markus moves a file and commits his changes.
Andreas changes the same file in the mean time, updates and commits.
There is no conflict no, warning - nothing. The changed files of Andreas
are not unter subversion's control anymore - very bad.

Although a conflict happend - both changed the same file in a way that
subversion cannot handle automatically - Andreas will not notice.
He will think everything is fine, but he can hit many problems:

1. His project will get strange compile errors.
2. His project will compile - he will get strange runtime errors.
3. His project will compile, no strange errors. Because he thinks, that
he finished his work, he gets a clean version. Now his changes are lost.
A couple of weeks later he will get a bug report for bugs he thought he
had fixed.

All these szenarios cost much effort and will ruin his confidence in the
development environment.

This wouldn't happen in CVS. A changed but deleted file is marked as a
conflict, which is probably the best way except defining a new state.
The developers who get conflict, know that they have a problem and that
they have to handle it. They cannot blame their revision control system,
when they spend much time searching for strange bugs or when they loose

What's the solution?


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Apr 16 09:43:32 2005

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