From: Ronald Landheer-Cieslak Sent: 22 July 2004 16:49
..snip..
OK, the problem is with CVS - the managed mounts are working properly.
CVS assumes Cygwin is/runs on a case-insensitive (file)system, which is
usually the case. On managed mounts, however, the assumption fails, and
CVS
-Original Message-
From: cygwin-owner On Behalf Of Hughes, Bill
Sent: 22 July 2004 17:24
From: Ronald Landheer-Cieslak Sent: 22 July 2004 16:49
..snip..
OK, the problem is with CVS - the managed mounts are
working properly.
CVS assumes Cygwin is/runs on a case-insensitive
On Thu, Jul 22, 2004 at 05:24:15PM +0100, Hughes, Bill wrote:
Yes, the problem is with CVS, not with Cygwin. Personally, I though
the first paragraph of the original post made that clear - apparently,
it didn't, so I apologize.
OT but possibly of interest, case-sensitivity (or otherwise) and how
Dave Korn wrote:
My ${CURRENCY_UNIT}*1e-2: rather than guessing, cvs should *find out*, by
creating a file in the current directory using a name that is known not to
exist, try to unlink it using a shifted version of that name, and then see
if it's gone or not. I *think* that would do the job,
On Jul 22 18:30, Dave Korn wrote:
No it isn't. NTFS is case *preserving*; neither NTFS nor windoze are case
*sensitive*.
That's only half the truth, though...
I am right that using the //./ notation invokes the NtCreateFile function,
aren't I? I think that's why the syntax works for
5 matches
Mail list logo
