9 messages in com.perforce.perforce-usercase (in)sensitivity
FromSent OnAttachments
Jame...@lads.com21 Mar 1999 16:47 
Babu...@Mitel.COMBabu_Somisetty22 Mar 1999 01:21 
Paul...@zergo.com22 Mar 1999 01:55 
Nick...@pobox.com22 Mar 1999 02:24 
Paul...@zergo.com22 Mar 1999 02:41 
Nick...@pobox.com22 Mar 1999 03:09 
Scot...@seanet.com22 Mar 1999 11:46 
Patr...@manage.com22 Mar 1999 12:05 
Scot...@seanet.com22 Mar 1999 17:39 
Subject:case (in)sensitivity
From:Paul...@zergo.com (Paul@zergo.com)
Date:03/22/1999 01:55:30 AM
List:com.perforce.perforce-user

Now I'm all for adding functionality to Perforce, but I think it's only fair to point out that Perforce's "problems" with the fact that Unix counts filename case as significant and NT doesn't are well documented.

It comes down to the fact that your actual files are stored in a server-native directory tree on your server.

Hence, if your client and server have different filename rules, you're restricted to the intersection of those rules, not the union.

If you're trying to do multi-platform development, then you need to account for the case sensitivity issues in your projects anyway.

If you're not doing multi-platform development, why are you using a server which has different filenaming conventions to the target you're developing on?

Paul.

-----Original Message----- From: Babu_Somisetty at Mitel.COM [mailto:Babu_Somisetty at Mitel.COM] Sent: 22 March 1999 09:21 To: jcej at tragus.org Cc: perforce-user at perforce.com Subject: Re: case (in)sensitivity

From: Babu Somisetty at MITEL on 03/22/99 01:21 AM PST I would like to add one more problem to this subject.

Say your p4d is on a UNIX box. You have two files dir_x/Makefile and dir_x/makefile in the same directory. If you run NT GUI you will only see one file with that name as opposed two files with different cases. Not only windows garbles the CASE, perforce client also garbles the fstat results from p4d. Go figure.

-babu

perforce-user at lads.com on 03/21/99 04:48:11 PM

Please respond to jcej at tragus.org

To: perforce-user at perforce.com cc: (bcc: Babu Somisetty/USA/Mitel) Subject: case (in)sensitivity

In one of my projects I have a Makefile and a makefile. This is on a Unix box but our repository is on NT. When I do 'p4 obliterate makefile', both of 'em go away. Ok, (a) it's really dumb to have both Makefile and makefile but I had good reasons at the time. And (b) 'p4 obliterate' shouldn't be used lightly. Still, it's kind of annoying that p4 ignored the casing and trashed both versions of the file. I think our server is version 98.2. Does anybody know if this has been fixed in one of the more recent versions? If not, is there a reason why it might not be fixed? We can hardly tell our developers to go back to the days of single-cased filenames! Thanks, J ============================================================== ========== This message has been processed by a mail-to-news gateway. The original sender (James CE Johnson ) can be reached via mailto:jcej at tragus.org ============================================================== ==========