[p4] does digest exist in depot

Matt Janulewicz matt.janulewicz at lucasfilm.com
Thu Aug 26 16:33:08 PDT 2010


It might be that the @= needs to be escaped (quotes.) What kind of error 
message does it give?

You could also try going old school and using the 'longhand' format (use 
a range, but specify the same changelist):

     //some/path/... at change, at change


-Matt Janulewicz
Lucasfilm Entertainment Company Ltd.


On 08/26/2010 04:29 PM, Christopher Evans wrote:
> I am trying to get the digest of a change-content trigger.
>
> The docs say:
> "Change-content triggers can access file contents by using the p4
> diff2, p4 files, p4 fstat, and p4 print commands with the @=change
> revision specifier"
>
> This doesnt work for me.. @ works, but it returns many diff changelists.
>
> CE
>
> On Thu, Aug 26, 2010 at 12:20 AM, Matt Janulewicz
> <matt.janulewicz at lucasfilm.com>  wrote:
>    
>> Do you mean you have the digest in hand and want to find the file that it's
>> associated with?
>>
>> 'digest' is one of the fields available to fstat, so you should be able to
>> search/filter with it. Something like this should do it:
>>
>>     p4 fstat -Ol -F "digest =<digest>" //some/path/...
>>
>>
>> -Matt Janulewicz
>> Lucasfilm Entertainment Company Ltd.
>>
>>
>> On 08/25/2010 03:01 PM, Christopher Evans wrote:
>>      
>>> Any easy way to simply ask the depot if a file with a hash digest exists?
>>>
>>> I would like to make a trigger that checks if a file exists on the
>>> server already. I was grabbing all files with the same name, then
>>> getting their digests, but sometimes the artists rename a file that is
>>> already in the depot.
>>>
>>>
>>>        
>>      
>
>
>    



More information about the perforce-user mailing list