Guten Tag Dave Tingling,
am Mittwoch, 11. Mai 2011 um 21:40 schrieben Sie:
>> When someone experiences the error, Their local copy will show as
>> modified immediately after the update, and attempting to commit the
>> working copy directory will include these changes. No conflict will be
>> detected.
I would try to test a bit: Take a dev where the file never was freaky
and let him produce small changes which are committable, e.g. add a
newline at the end of the file and remove it or stuff like that. But
it should be always the same changes. After each change let your
problematic developer N update the file and see if the error happens
and if it always results in the same wrong changes.
I can't believe the error is in the subversion code, sounds more like
a client problem to me. Client side scripts, programs locking the file
and all that kind of stuff.
Mit freundlichen Grüßen,
Thorsten Schöning
--
Thorsten Schöning
AM-SoFT IT-Systeme - Hameln | Potsdam | Leipzig
Telefon: Potsdam: 0331-743881-0
E-Mail: tschoening@am-soft.de
Web: http://www.am-soft.de
AM-SoFT GmbH IT-Systeme, Konsumhof 1-5, 14482 Potsdam
Amtsgericht Potsdam HRB 21278 P, Geschäftsführer: Andreas Muchow
|