[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: cvs [server aborted]: <file-name>,v is ambiguous
From: |
Terrence Enger |
Subject: |
Re: cvs [server aborted]: <file-name>,v is ambiguous |
Date: |
Tue, 24 Jun 2003 18:36:23 -0400 |
At 09:22 2003-06-24 -0700, "Mark D. Baushke" <mdb@cvshome.org> wrote:
>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.
[snip]
>> 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.
[snip]
>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?
Well, that might be me, depending on how you define IBM mainframe.
The IBM iSeries may be case-sensitive, case-preserving, or case-folding,
depending on where the repository or sandbox is within the file system.
Moreover, parts of the file system impose draconian constraints on the form
that names may take. I shall have to face this before my work is done, and
I expect a solution will require quite some work. In particular, cvs will
not know just how to work until it has (at least the leading parts of) a
directory name in hand. However, I expect cvs to be useful before it has
this flexibility.
Meanwhile, I am working exclusively in the case-preserving part of the file
system, and I have not invested any effort toward working any other way. I
expect that this discussion, and any code changes arising from it, will
make my job easier.
Thank you, all, for your consideration.
Terry.
Available for contract programming.