Justin Erenkrantz wrote:
>
> The key is to not let those files in the repos at all -
For a particular project, the administrator might want to ensure that some or
all files are named so as to be accessible on every possible platform; that's
fine. However, most repository administrators, and certainly Subversion
itself, should definitely not restrict all file names in this way. Except in
very closed environments, at commit time nobody knows on what filesystem
someone might later check out the project. That would mean that the only safe
filenames are "lowest common denominator" names, and I think that is unacceptable.
> [If they] make it in, then the WC isn't going to be able to do much. There
> is no accurate way to determine what FS you are on in any case, so
> it's not likely that the WC can do much other than panic. =) --
It may be true that there is no accurate way to determine what FS "you are on"
(more precisely, on which a particular file is stored). It is wrong to imply
that the WC can't cope. There are all sorts of ideas for what the WC could do.
Here's my addition to these ideas: The WC has a concept of a "missing" file
that is used when the user doesn't have read access to a particular file in the
repository. The WC knows that such a file exists in the repos but is not
present in the WC. Leaving an incompatibly-named file out of the WC and using
this "missing" status seems like a possible part of a solution.
- Julian
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Feb 7 23:27:09 2006