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

Re: [TSVN] Delete/modified conflicts handled poorly

From: Stefan Küng <stefan.kueng_at_wagner-group.ch>
Date: 2004-08-19 10:26:18 CEST

Timothy B K. Kientzle wrote:

> If a file is deleted in the repository,
> and the local working copy is modified,
> then the following problems occur:
>
> * Attempts to commit from the local working copy lead
> to an inscrutable error message.

"File not found" isn't that bad.

> If you then use either the Explorer Delete operation
> or the Tortoise Delete operation, then the
> following further problems occur:
> * Commit fails

tried with RC1 - works ok.

> * Update fails

works ok too.

> (Alternatively, have someone checkin foo.obj
> to a project, and then try to delete it while the
> developers are innocently rebuilding. And then
> tell them that you deleted the file... Watch
> those developers spend the entire day downloading
> a new copy of a 300MB project over a slow connection. ;-)

And then slap those people because they haven't read the docs. When a
commit fails (for whatever reason), the very next step should be an
update and not some tweaking/deleting without knowing what they really do.

> FYI:
> TortoiseSVN 1.0.3, Build 1430, UNICODE

Don't you have an older version lying around which you could use?

> Subversion 1.0.6 (r10360)

You update Subversion, but not TortoiseSVN?

Stefan

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Thu Aug 19 11:25:35 2004

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.