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

Re: svn co win32 and linux filesystem compatibility question

From: v4r4n <console.cowboy_at_gmail.com>
Date: 2006-01-05 20:03:54 CET

Wow, I tried what you said. That is really scary. You'd think they'd have
fixed something like that, but they obviously don't believe it is important.


Turns out my problem was just a case insensitivity issue. Of the 1400+
files, 7 of them were lower case copies of upper case versions.

By unzipping a compressed tar ball of the linux source on windows, I was
able to see which specific files were causing the problems.


On 1/5/06, Scott Palmer <scott.palmer@2connected.org> wrote:
> On 4-Jan-06, at 10:16 PM, v4r4n wrote:
> >
> > Other than these characters \ / * ? | " < > : does windows xp have
> > other possible issues with *nix compatible file names?
> Yes, Windows is completely brain-dead with regards to the filesystem.
> Other files that will cause problems are
> COM1
> COM1.*
> COM2
> COM2.*
> ...
> LPT1
> LPT1.*
> PRN.*
> It does not matter if you specify a full path, e.g. C:\my_app
> \communication_settings\COM1.xml, is not allowed.
> This stupidity comes from the ancient DOS roots of Windows and the
> fact that they allowed names like COM1 instead of requiring a colon,
> like for driver letters (don't get me started on that crap). Ie. if
> "COM1:" were used instead of "COM1" there wouldn't be this mess.. but
> that's not the case.
> Scott.
> (sometimes I miss tmy C= Amiga)
Received on Thu Jan 5 20:59:36 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.