8 messages in com.perforce.perforce-userNT/UNIX Case Sensitivity Experiences| From | Sent On | Attachments |
|---|---|---|
| EdMa...@wrq.com | 04 Nov 1998 15:44 | |
| Eric...@Adobe.COM | 04 Nov 1998 15:57 | |
| AmyS...@ISRWORLD.com | 04 Nov 1998 16:00 | |
| Chas...@luna.com | 04 Nov 1998 17:06 | |
| Davi...@home.chat.net | 04 Nov 1998 17:11 | |
| EdMa...@wrq.com | 04 Nov 1998 17:20 | |
| Jerr...@esd.sgi.com | 04 Nov 1998 17:23 | |
| Jerr...@esd.sgi.com | 04 Nov 1998 17:59 |
| Subject: | NT/UNIX Case Sensitivity Experiences![]() |
|---|---|
| From: | Davi...@home.chat.net (Davi...@home.chat.net) |
| Date: | 11/04/1998 05:11:32 PM |
| List: | com.perforce.perforce-user |
On Wed, Nov 04, 1998 at 03:44:29PM -0800, Ed Mack wrote:
Once a directory exists on a Wintel machine, does MS-DevStudio ever change the case of directories or filenames--in the project's .DSP, thus confusing Perforce when opening files for add or edit?
I've not had problems with the user and client names, because I explicitly set them. However, I have had problems with the case of directories or filenames. Particularly if some files are added via the command line and some are added via the MSDEV GUI.
I've mailed my case solution idea to perforce support, I don't know if they have any plans to implement it. It was targeted at this directory/file stuff, but would apply equally well to p4user and p4client.
Here is the text of my suggestion:
The 'real behavior' I want is to have the operations be case-insensitive or not based on the case-insensitivity of the client, not the server. In fact, I would prefer if there were a way to handle case sensitive clients from a case-insensitive server like NT. (although I would never use NT for a server myself).
For example, the NT perforce server could just replace all uppercase letters with "$<lettter>" so that if I checked in:
FooBar.h
It could turn it into:
$foo$bar.h
I don't know what the best character to use for "$" is, but any character which is a valid filename character on NT, but not a valid Perforce character would be fine.
Then, perforce should be capable of performing the case-insensitive matching for case-insensitive clients on commands like: add, delete, edit,
--- David Jeske (N9LCA) + http://www.chat.net/~jeske/ + jeske at chat.net




