>>>>> "A" == A T Hofkamp <A.T.Hofkamp> writes:
A> Paul Koning wrote:
>> Case issues are one cause of this. Unicode encoding problems are
>> another. But converting file names to a single form won't help
>> that. You could help it by converting file names that clash to
>> unique names, like filen~01.txt... :-) but that's rather ugly...
A> I think the whole point is that clashes cannot be prevented. So
A> when it happens, imho svn should be able to create a consistent WC
A> (without loss of data/files) eg by creating ugly filenames. Then
A> everybody can grab their filename-coding-standard copy, figure out
A> who to blame, fix the problem, and get on with their life ;-).
A> Another point w.r.t. case-sensitivity may be that svn may need a
A> bit of configuration to understand that some file systems are not
A> very good at remembering the exact filename. Maybe we should have
A> a config flag
A> [working-copy] filenames=case-insensitive
A> and the other one
A> [working-copy] filenames=exact
A> so users can specify what they want.
I suppose that could be done, but why? I don't know of any supported
OS that has a file system like that. If you wanted to port Subversion
to VMS, this could become an issue, but until then, I believe all the
file systems are at least case-preserving.
Mac OS X isn't encoding-preserving, though, which is an issue for
non-ASCII filenames -- as was previously noted. That's where the
scheme you mentioned -- keeping the repository filename in the .svn,
and recognizing that the local filename may be different -- would
help.
paul
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Dec 15 16:17:18 2005