-----Original Message-----
From: jab [mailto:jab at pobox.com]
And when you exclude something, you give both fields again, to say
something like "look, I'm not pulling down
//depot/dir1/excludeme/..."
AND TO BE PRECISE it would've landed at //cws/excludeme/... but
nothing's mapped there now, okay?"
I agree that the first column should imply the second, but the
parsing code wants to see two fields...
I don't think it's just for symmetry of syntax, either.
Some errors I've gotten make it seem obvious that some
operations look only at the left and some only at the
right while searching for the last matching line. That
means, if exclusion lines only had one field, the file
would have to parsed first to convert a local path to
a depot path, then again to look for a possible
exclusion line. More efficient to make it explicit on
both sides. -Wm
5 messages in com.perforce.perforce-user[p4] Nagging question about client vi...