[p4] Patching files checked out from Perforce with no questions asked

Geir A. Myrestrand geir.myrestrand at falconstor.com
Wed Nov 1 13:20:10 PST 2006


Andrew May wrote:
> On Wed, Nov 01, 2006 at 11:57:27AM -0500, Geir A. Myrestrand wrote:
>> Upon applying a rather large patch set on files checked out from 
>> Perforce, I am presented with this question for every file modified by 
>> the patch set:
>>
>> Get file <filename_modified_by_patch_set> from Perforce with lock? [y]
>>
>> The desired behavior is no, but I don't want to answer this question for 
>> each file in the patch set --I want no for all, without the interactive 
>> portion.
> 
> How about changing the clientspec to remove/change the "noallwrite" and allow
> all the files to be writable. It seems you don't want the changes under perforce
> control at all.

I don't need the patched files to be under Perforce control, but I do 
want the other files I checked out to be under Perforce control.

> There is also the "-V method  or  --version-control=method" option to patch
> itself. "-V never" may get rid of it too.

I followed Jason Williams tip of setting the PATCH_GET environment 
variable to 0 (zero), and that solved the issue.


-- 

Geir A. Myrestrand


More information about the perforce-user mailing list