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

Re: loss of committed changes

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2004-11-12 17:37:14 CET

On Nov 11, 2004, at 12:21 PM, mike south wrote:
> but yesterday when bunch of developers were working, often in the
> same file, we would see changes disappear quite frequently.

I have to admit, I'm skeptical. If such a bug existed, it would be so
incredibly fundamental to svn's core abilities, it should have been
noticed a hundred times over the course of 4 years of development and

I'm not pooh-poohing your problem; I really do believe that you guys
are seeing changes disappear, and are frustrated. But historically,
any time folks have ever complained about something like this, it's
almost always because of some human error or silly mistake. For
example, we seen cases where users get conflicts, get confused about
how to deal with conflict markers, and toss away other users' changes
without realizing it. Or they accidentally copy old versions of files
on top of working files, again destroying newer changes. A lot of odd
things happen.

I guess I'm just saying the the probability of a bug of this magnitude
existing is extremely tiny, compared to the probability of PEBKAC.
Don't take it personally. :-)

The best thing to do is keep a watchful eye... the *instant* something
suspcicious happens, have your user save the output of shell 'history'
somewhere... it's the beginning of a transcript that can help us either
detect PEBKAC or a reproduction recipe.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Nov 12 17:37:41 2004

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.