[p4] perforce vs. subversion

Knut Forkalsrud kforkalsrud at cj.com
Wed May 3 13:15:43 PDT 2006


"Jeff Grills" <jgrills at junctionpoint.com> writes:

> You can always write a perforce trigger that will forbid the
> submission of a changelist which contains files you know should
> never be submitted.
...
> Another thing that may be feasible (though I've never tried) is to
> unmap those files from your perforce client with an exclusionary
> mapping

Both of these are good, I just started using the client exclusionary
mapping myself and it is pretty close to what I'm looking for.  Thanks
a lot.


The problem now is my "p4unmapped" command, which I picked up from
this list.  In bash:

alias p4unmapped=\
 'find * ! -type d | p4 -x - files 2>&1 > /dev/null | cut -f1 -d" "'

This still shows the files even though they're not mapped in my client
spec...

I'm inclined to say that this functionality should be part of the
standard perforce client.

Thanks again,

-Knut


More information about the perforce-user mailing list