[Top][All Lists]

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

Re: cvs [server aborted]: <file-name>,v is ambiguous

From: Mark D. Baushke
Subject: Re: cvs [server aborted]: <file-name>,v is ambiguous
Date: Tue, 24 Jun 2003 09:22:52 -0700

Larry Jones <lawrence.jones@eds.com> writes:

> Derek Robert Price writes:
> > 
> >  Larry, you recently expressed a wish to me that case-insensitive file 
> > systems would just go away.  Does anybody have a good feel for what 
> > would happen if we removed case-insensitivity awareness from the server 
> > altogether and let the client deal with it?  I think that since Windows 
> > is now (or always was?) case-preserving, there mostly shouldn't be a 
> > problem, aside from possibly having to educate users that they have to 
> > get the case correct on the initial checkout.
> There are other case-insensitive systems that are *not* case preserving,
> notably VMS (and the IBM mainframe systems if whoever is working on
> porting CVS to that environment ever succeeds).
> I think someone really needs to think about the 9 possible cases -- case
> insensitive but case preserving, case insensitive case folding, and case
> sensitive clients and servers -- and figure out how CVS should behave. 
> Once we've decided what it's *supposed* to do, then we can make it do
> it.  "Let's try this and see how it works out" is how we got where we
> are now, I'm not convinced it's a viable method for improving the
> situation.

It seems a reasonable idea, to me. Do we have anyone out there working
on the VMS and IBM mainframe systems that have input on this?

        -- Mark

reply via email to

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