Comments on: //projectfoo/bar/… – must refer to client ‘p4_client’. http://allscm.com/archives/projectfoobar-must-refer-to-client-2.html SCM Unleashed! Wed, 17 Feb 2010 12:11:02 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: Charles http://allscm.com/archives/projectfoobar-must-refer-to-client-2.html/comment-page-1#comment-7 Charles Thu, 16 Apr 2009 04:58:14 +0000 http://allscm.com/?p=118#comment-7 I meant the OS of the system your Perforce server is on, not the client system. But as I said... I may be wrong. I meant the OS of the system your Perforce server is on, not the client system. But as I said… I may be wrong.

]]> By: Davy http://allscm.com/archives/projectfoobar-must-refer-to-client-2.html/comment-page-1#comment-6 Davy Thu, 16 Apr 2009 03:54:44 +0000 http://allscm.com/?p=118#comment-6 I actually received the same errors in both Windows and Solaris. Although while in Windows, I was under Cygwin. I actually received the same errors in both Windows and Solaris. Although while in Windows, I was under Cygwin.

]]> By: Charles http://allscm.com/archives/projectfoobar-must-refer-to-client-2.html/comment-page-1#comment-5 Charles Wed, 15 Apr 2009 10:18:54 +0000 http://allscm.com/?p=118#comment-5 Just a small clarification on this one: I'm assuming your client spec definition is //ProjectFoo/... //[some_p4_client]/... If so, ‘p4 changes //ProjectFoo/BAR/…@xxxxxx,yyyyyy’(BAR in wrong case) will work without errors, and you will get 0 results The reason you get the error with your original query is that //projectfoo is actually outside your clientspec definition I may be wrong on this point, but I think that the case sensitivity has to do with the OS your Perforce server is based on rather that Perforce itself. If it's a Windows OS, then I think it allows wrong casing for queries Just a small clarification on this one:

I’m assuming your client spec definition is
//ProjectFoo/… //[some_p4_client]/…

If so, ‘p4 changes //ProjectFoo/BAR/…@xxxxxx,yyyyyy’(BAR in wrong case) will work without errors, and you will get 0 results

The reason you get the error with your original query is that //projectfoo is actually outside your clientspec definition

I may be wrong on this point, but I think that the case sensitivity has to do with the OS your Perforce server is based on rather that Perforce itself. If it’s a Windows OS, then I think it allows wrong casing for queries

]]>