Re: RFC: Reworking server handling of case insensitive clients

[Derek Robert Price]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Derek Robert Price wrote:

| Additional Notes
|
| It turns out that the CVS client/server protocol specification
specifies that
| clients will preserve case in Entries, so the server may count on this
behavior
| and use that filename value to look for archives case-sensitively
rather than
| going through the case-insensitive lookup and thus the filter
functions.  This
| fix may be viable on the stable branch if not already implemented
correctly.


Does anyone know whether most CVS clients are preserving the server's
file case in CVS/Entries as doc/cvsclient.texi specifies they should?
I'd like to fix the stable branch to rely on this feature of clients,
but I would not want to release a new stable release that was suddenly
incompatible with most clients, regardless of whether those clients are
broken or not.

Derek
- --
~                *8^)

Email: derek@ximbiot.com

Get CVS support at <http://ximbiot.com>!
- --
I am not a 32 year old woman.
I am not a 32 year old woman.
I am not a 32 year old woman...

~          - Bart Simpson on chalkboard, _The Simpsons_
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Using GnuPG with Netscape - http://enigmail.mozdev.org

iD8DBQE/gsNPLD1OTBfyMaQRAspkAKCxlQPq9NHHBtflcYNdqkKNS4dNWQCg9/qj
73PaURJYZf2lr+9KSzQC3Wg=
=anKZ
-----END PGP SIGNATURE-----