[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: D.J. Heap <djheap_at_gmail.com>
Date: 2006-07-26 20:12:12 CEST

On 7/26/06, Bill Ewing <bewing@nexusbio.com> wrote:
>
> Trevor wrote: "Can you tell us exactly what you are trying to do when you
> come across these
> problems. If you are modifying the structure of directories/renaming files
> you need to make sure to do it using the tools. Either by using tortoise to
> rename them, or having subclipse rename them. This way they will know what
> the other is doing. If you are just moving files using file system
> commands, then neither will know what's going on."
>
> 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.
>
> I will concede that source control typically means the files live in the
> working area and are not frequently transplanted.
>
> 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.
>
> To correct our problem, we delete everything and then very carefully rebuild
> it all, stopping to let SVN know what's going on at every microstep. This
> feels like it is us who serve SVN and not the other way around, but a zero
> cost, I guess we can't complain.
>
> 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?
>

I think that the main problem is that Subversion keeps all it's
knowledge inside the folders you are deleting and moving etc. -- so
you are essentially lobotimizing it and then asking it to grow a new
brain automatically.

I'm pretty sure there is an issue already filed about making
Subversion keep it's knowledge somewhere else rather than inside the
working copy so that shuffling and deleting folders won't be such a
problem. I believe someone did work on it for a while and was making
progress, but they dropped it as far as I know.

If you are interested enough you could research that issue and
followup on it with the design and details on how it would work and
post it to the dev list and then maybe someone will pick it up and
work on it.

DJ

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jul 26 20:13:53 2006

This is an archived mail posted to the Subversion Users mailing list.