Kuros Yalpani wrote:
> For some strange reason, the cvs server (Unix) makes a decision about case
> insensitivity
> and it ought not. The cvs client should decide when two filenames are "equal" and
> not the
> server. The server is not doing anything wrong by being case sensitive.
I didn't code it myself, but I'm guessing that it's that way for something like the
following reasons:
1) Handling of case insensitive clients was added as an afterthought and the
CVS client/server protocol was already in production. Thus, since the client sends a
list of file names it wants updated to the server, the server had to be aware that the
client was case insensitive to do the matching.
2) When the alternative to the above (sending a list of available files to the client
and allowing the client to return a correctly cased list of desired files) was
considered, it was discarded since one of the aims of the CVS client/server protocol
is to minimize network transfer.
3) The conceptual model of CVS as an interface to another filesystem seemed workable
(I'd say it still is, mostly), and since the local system was case insensitive, CVS's
view could be too.
Derek
--
Derek Price CVS Solutions Architect ( http://CVSHome.org )
mailto:[EMAIL PROTECTED] OpenAvenue ( http://OpenAvenue.com )
--
The principal's toupee is not a Frisbee.
The principal's toupee is not a Frisbee.
The principal's toupee is not a Frisbee...
- Bart Simpson on chalkboard, _The Simpsons_
_______________________________________________
Bug-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-cvs
