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...
Ugly but working.
I think the whole point is that clashes cannot be prevented.
So when it happens, imho svn should be able to create a consistent WC (without
loss of data/files) eg by creating ugly filenames.
Then everybody can grab their filename-coding-standard copy, figure out who to
blame, fix the problem, and get on with their life ;-).
[note that as soon as an administration is created for the 'real' filename
versus the repo filename such as for above, this would also be a nice hook for
creating files at a totally different place, ie away from the dir with the
.svn entry as discussed recently (opaque filenames I believe it was called).
]
Another point w.r.t. case-sensitivity may be that svn may need a bit of
configuration to understand that some file systems are not very good at
remembering the exact filename.
Maybe we should have a config flag
[working-copy]
filenames=case-insensitive
and the other one
[working-copy]
filenames=exact
so users can specify what they want.
Albert
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Dec 15 09:29:50 2005