I'm running Eclipse on OS X and I've seen half a dozen instances of
corrupt files being committed ... i.e. file data that's different from
the working copies.
The corruption manifests itself as a truncated file with some lines in
the header ( e.g. $Revision lines) also being garbled. I always have to
fix with a reverse merge since the working copies are not corrupt
(unless the bad commit is checked out, of course).
I've seen this on two different OS X systems now, one 10.3.7 and one a
completely clean install of 10.3.8, so the problem isn't isolated to
the quirks of one installation. Unfortunately I don't know exactly what
sequence of events will cause a bad commit, yet, although I've seen it
on at least three files in the last week (all C++ .h). I've yet to see
a corrupt commit from the CLI client, so I'm suspecting the Eclipse
subsystems at the moment.
Obviously this is a serious problem for me, I kind of hope no-one can
reproduce this nasty behaviour, but on the other hand, I'd feel even
better if it were reproduced and fixed.
Received on Wed Mar 9 03:02:23 2005