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

RE: What to do when Update, Clean, Resolve everything else does not work?

From: Bill Ewing <bewing_at_nexusbio.com>
Date: 2006-07-26 22:58:11 CEST

Thank you Ryan for this explanation.

-----Original Message-----
From: Ryan Schmidt [mailto:subversion-2006c@ryandesign.com]
Sent: Wednesday, July 26, 2006 11:25 AM
To: bewing@nexusbio.com
Cc: users@subversion.tigris.org
Subject: Re: What to do when Update, Clean, Resolve everything else does not
work?

On Jul 26, 2006, at 19:37, Bill Ewing wrote:

> The thing we are doing "wrong" seems to be using an external tool like
> Windows Explorer to delete a folder that is under source control and
> then replace it.

Yes; that would be a no-no.

> The disturbing thing is this: by a series of very normal file
> management actions, it is foolishly easy to put subversion into a
> state in which it simply cannot offer adequate means to fight your way
> out of.

Subversion is designed so that you will use its own commands whenever you
want to remove or rename files or directories, and that you are not to use
other means to do this, such as Windows Explorer.

> What I wish SVN could do is figure things out when:
> 1. We delete a folder.
> 2. We replace the folder with a new folder of the same name. Some of
> the files within it match what was there before, and some don't.
> 3. We tell SVN to do a Clean Up or Update or some simple command 4. We
> are able to commit the files
>
> How hard is that? Doesn't it seem like a robust source management
> tool would handle this in stride?

No; at least, not Subversion. This FAQ entry may be relevant:

http://subversion.tigris.org/faq.html#wc-change-detection

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jul 26 22:59:35 2006

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.