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

Re: [PATCH] First step for issue #3702 (case-only renames on Windows) - now blocked by libsvn_client

From: Branko ─îibej <brane_at_e-reka.si>
Date: Sat, 16 Apr 2011 16:35:43 +0200

On 16.04.2011 16:14, Johan Corveleyn wrote:
> Do I have to worry about differences between on-disk casing and wc-db
> casing of a path? Is that possible? I guess it is by using non-svn
> commands, but I bet that's an invalid state of the wc (I know that in
> 1.6, if you run into this, svn gets all confused (marking the file it
> has in metadata as deleted, and your on-disk file as unversioned)).
> That's definitely out of scope for the change I'm trying to make.

"Valid state" is kinda fuzzy, and since some tools (still) insist on
changing file case every which way, this case can realistically be
expected to happen every once in a while. But certainly more than just
rename are affected by it, so I guess it's not realistic to try to deal
with the problem in your patch.

The most famousest case where this can happen is if you try to check out
"Foo" and "fOO" in the same directory on a case-insensitive file system.
Our answer to that has been, "don't do that"; and it would take very
significant surgery in the client and WC libraries to make it work. I'm
unaware of any version control system that handles such cases correctly.

By the way, does your patch deal with the case where an "svn update"
results in a case-only rename?

-- Brane
Received on 2011-04-16 16:36:21 CEST

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

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