bug-cvs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: RFC: Reworking server handling of case insensitive clients


From: Jim.Hyslop
Subject: RE: RFC: Reworking server handling of case insensitive clients
Date: Tue, 7 Oct 2003 11:28:16 -0400

Derek Robert Price [mailto:address@hidden wrote:
> I just noticed that the mistake I apparently made from
> 1.11.5 to 1.11.6 in fixing the add problem, to my chagrin, was that I
> deleted the portion of the code that preserved CVS/Entries 
> entries case
> as passed by the client.  Fixing that now.
I should have specified which version of the client I was using - 1.11.5. I
never noticed the problem you mentioned.

BTW, will this effort fix this problem:

D:\files\cvs\cvs-test>cvs-1.11.5 st jhyslop/mixedcase
===================================================================
File: no file mixedcase         Status: Needs Checkout

   Working revision:    No entry for mixedcase
   Repository revision: 1.2     /cvs/cvs-test/jhyslop/MiXeDcAsE,v


D:\files\cvs\cvs-test>cvs-1.11.5 st jhyslop/MiXeDcAsE
===================================================================
File: MiXeDcAsE         Status: Up-to-date

   Working revision:    1.2
   Repository revision: 1.2     /cvs/cvs-test/jhyslop/MiXeDcAsE,v
   Sticky Tag:          (none)
   Sticky Date:         (none)
   Sticky Options:      (none)


i.e. if I am working in a different directory, I must be case-correct when
specifying filenames. The interesting thing to note is that in the first
command, the client (1.11.5 again, BTW) finds the correct line in the
Entries file - note that in both cases, it correctly reports the repository
version as 1.2. The fix seems fairly easy - when sending the 'Argument
jhyslop/mixedcase' convert it to the correct case, extracted from the
Entries file (mind you, I haven't looked at the code to see if it is as easy
as it appears to be :-).

-- 
Jim




reply via email to

[Prev in Thread] Current Thread [Next in Thread]