Max Bowsher <maxb1@ukf.net> wrote:
>> P.S. If you were interested in supporting case-sensitive file names
>> also (i.e. having two files in the same directory that only differ
>> in case): that would be possible through FILE_FLAGS_POSIX_SEMANTICS
>> for CreateFile - unfortunately, you would have to use NtDeleteFile
>> for removal...
>
> Sure, you can play all sorts of devious tricks with low level APIs,
> but that leaves you with files on your disk that cause 99% of existing
> software tools to then break in mysterious ways when you attempt to
> work with them.
>
> In my personal opinion, this 'solution' is totally nonviable.
I don't understand. It's not that Subversion is *creating* files with weird
filenames out of the blue. If *I* added it to the repository, it means that *I*
have tools to handle them. *I* will also make sure other people accessing the
repository know what to do with them. It could also be that those files can't /
needn't be accessed at all under Windows and people will access them under
different OS: if this is fine by me (in my repository), I'm not sure why you,
as a Subversion developer, should care. It's up to the users to decide what to
do. If I know how to create files with trailing dots, well, let me shoot myself
in the foot, don't tell me that I should be playing nice.
I believe Subversion should do everything in its power to behave correctly,
even with respect to files with wrong filenames. Surely being unable to check
out the correct files, and then complain because the repository is changed
while it really isn't, doesn't look like a correct behaviour.
Giovanni Bajo
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Jan 21 09:21:37 2006