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

Re: Question about WC changes going into SVN 1.6

From: Branko Čibej <brane_at_xbc.nu>
Date: Fri, 10 Oct 2008 15:04:39 +0200

Mark Phippard wrote:
> Sorry for the drive-by, but this just popped into my head as I was
> thinking about the wc-ng stuff a bit.
>
> I believe one of the changes going into 1.6 has to do with the
> management of the text-base (using SQLite). I was wondering if that
> included discontinuing the use of the file name in the name of the
> file in text-base? If we did this, that would presumably resolve the
> case-sensitivity problems we have on Windows and OSX.
>

It would resolve some of the case-sensitivity problems, yes. It won't
solve the "files in same dir differ only in case" issue, nor the nastier
one where the user (or some tool) changes the case of a filename in the
WC and then we don't find the file in entries any more. And note that
these are not limited to Windows amd Mac, they can happen, e.g., on
Linux on a case-insensitive filesystem (e.g., FAT, or CIFS mount).

IMHO that last one can only be solved by actually trying to stat the
files that are flagged as missing after a status tree walk. If it's only
a case change, and the filesystem is case-insensitive, the stat will
succeed and you'll even get the new file name back. Note that a
case-insensitive name compare is *not* enough because there's no
guarantee that the filesystem will do the same kind of case folding that
your locale does; for example, NTFS has a fixed, per-volume casefold
table that's independent of locales.

-- Brane

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-10-10 15:04:55 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.