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

Re: checkout of revisons<HEAD with case conflicting filenames on Windows

From: Duncan Murdoch <subversion_at_murdoch-sutherland.com>
Date: 2005-11-27 00:18:35 CET

On 11/26/2005 6:00 PM, h.larsen@risoe.dk wrote:
> Take an example repository:
> Revision 1: file.txt:1; FILE.TXT:1;
> Revision 2: file.txt:2; FILE.TXT:1;
> Revision 3: file.txt:3; FILE.TXT:1;
> As seen, there are files which differ only in case. On Windows this is
> problematic due to the case-insensitive file system. There are ways to
> get
> around this problem as described in the svn-faq WHEN its concerning the
> LATEST revision (3).
> But how to solve the problem of making a checkout of revision 1 or 2 on
> a windows platform?
> You can't rename or delete anything in revision 1 or 2 to make it
> windows compatible. Its history, it can't be changed. The only solution
> I have found is to:
> 1) Create a branch copy of the old revision
> 2) Patch it up to remove any conflicting case issues for instance by
> rename or deletion of problem files. This seems possible as it is
> 3) Now its possible to checkout onto windows file system
> Is this really the only solution, except of course involving a
> unix/linux box?

I'm curious, what happens when you try to check out one of those
revisions? Does the checkout fail, or do you get everything except only
one of file.txt and FILE.TXT? Does the name match the one you get?

If the latter, I imagine you could copy just one of the files rather
than the whole project, but I can't think of any way Subversion could do
something better. Windows won't let you have both file.txt and FILE.TXT
in the same directory.

Duncan Murdoch

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Nov 27 00:20:16 2005

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.