Peter N. Lundblad <mailto:peter@famlundblad.se> wrote on 24 November 2004
21:06:
> I am definitely with sussman here (his original proposal). I
> see no reason
> at all to support control characters. I think it is a mistake
> of an OS to
> support them in filenames, but that's another discussion. They are
> problematic in our dump format (if I understand correctly), we have to
> deal with them in the entries files, we'd have to deal with
> them in DAV
> and probably have interop problems with other DAV
> implementations and they
> confuse people.
I have little opinion on control characters (apart from thinking that having
your computer beep out a rhythm to you when you type "ls" has a certain
quality to it!), but on the general subject of making repositories "safe" to
particular filesystems (be that NTFS, ext*, or whatever), would it be a good
idea to have a per-repo setting for which filesystems it absolutely *must*
work with. For example, a repository which must work with Windows-y file
systems would ban symlinks (and perform case-protection), while a repository
which must work with another type of file system might ban filenames with
whitespace, or whatever is necessary.
IMHO, this makes sense because whether this is implemented or not, the
verification that all users of the repo can check it all out must be
performed (i.e. the lowest common denominator must be used for all
filesystems across a single project) - it's just that at present, this has
to be implemented manually by the user (or by hooks - maybe there are
standard hooks already written to do this?).
Adds/moves could then be verified against the spec set by the repository.
Just my .02
Ben Sewell
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Nov 25 11:00:35 2004