Jump to content


Member Since 01 Mar 2013
Offline Last Active May 30 2019 08:32 PM

Topics I've Started

P4V - about p4diff command line options

26 April 2019 - 07:18 PM


I have a file //mydepot/mybranch/myfile.txt opened for edit with just a single whitespace change.
When I run the command
p4 diff -sr //mydepot/mybranch/...
it returns nothing because myfile.txt has been changed with a white space..

But if I include the options -db -dw -dl, perforce still returns nothing. It seems that these options are not compatible with -sr.

i.e.: p4 diff -db -dw -dl -sr //mydepot/mybranch/...

Is there a way that I can return the list of unchanged files from perforce ignoring all whitespace changes?


-Jonathan Wilson

P.S. I'm using P4V on Windows 10 Rev. P4V/NTX64/2018.4/1753667

Command line version:
F:\P4\mywork>p4 -V
Perforce - The Fast Software Configuration Management System.
Copyright 1995-2019 Perforce Software.  All rights reserved.
This product includes software developed by the OpenSSL Project
for use in the OpenSSL Toolkit (http://www.openssl.org/)
Version of OpenSSL Libraries: OpenSSL 1.0.2q  20 Nov 2018
See 'p4 help [ -l ] legal' for additional license information on
these licenses and others.
Extensions/scripting support built-in.
Parallel sync threading built-in.
Rev. P4/NTX64/2018.2/1751184 (2019/01/21).

P4V Undo changes does nothing for mixed depots

15 March 2019 - 09:34 PM


I'm currently using P4V Rev. P4V/NTX64/2018.4/1753667 on Windows 10 and my server version is P4D/LINUX26X86_64/2016.2/1568552 (2017/09/20).

I wanted to revisit an issue that I reported last year https://forums.perfo.../page__hl__undo

I was able to determine that P4V's "Undo Changes..." operation does nothing on a submitted changelist that contains files from 2 different depots but running the operation on command line works fine
i.e.: p4 undo -c 562745 //...@562353

I was wondering if this issue was addressed or being looked at?


-Jonathan Wilson

P4V reconcile inconsistency

07 February 2019 - 04:46 PM


I am currently using P4V version Rev. P4V/NTX64/2018.4/1753667 on Windows 10 and my server version is P4D/LINUX26X86_64/2016.2/1568552 (2017/09/20)

I seem to be experiencing a strange inconsistency with the p4 reconcile operation.
When I select the Reconcile Offline Work from P4V the operation works as expected (see attached screenshots 1, 2, and 3)

However when i try to run the same command from the command line (after selecting Open Command Window Here) nothing get reconciled.


p4 reconcile -c 1205131 -a -d -e -f //mydepot/SubmitAssistant/Default/...
//mydepot/SubmitAssistant/Default/... - no file(s) to reconcile.

Would anyone have any idea why the operation doesn't work via the command line?

Let me know if you need any additional information.


-Jonathan Wilson

Swarm - Unable to download zip file

14 January 2019 - 10:12 PM


I am currently using Swarm Version 'SWARM/2018.1/1660025 (2018/05/09)' on Perforce server version P4D/LINUX26X86_64/2016.2/1568552 (2017/09/20).

On a particular swarm review I cannot seem to download the zip file attached to the review (see attachments).

The full error message is:
Error: Failed to archive '/opt/perforce/swarm-dunia/data/clients/6A77696C736F6E/swarm-459792cd-dddb-0dd4-6307-553c6466f255/turing/dev/main/Code/AgentGroupImpl/SupportServices/CloakSupportGroupDataModule.criteria.generated.cpp'. Exit status: 12. Output: zip error: Nothing to do! (try: zip -y -1 -r /opt/perforce/swarm-dunia/data/cache/archives/swarm-review-1461142.zip . -i CloakSupportGroupDataModule.criteria.generated.cpp)

The error message seems to be related to a file that was moved/renamed (attachment #3). Is there any way to resolve this issue?

Let me know if you need any additional information.


-Jonathan Wilson

Question about restricting submits from specific folders using wildcards

03 December 2018 - 07:42 PM


I would like to restrict submits to 2 particular folders using p4 protect.

The folders are:


In this example I would just do

=write group * * -//mydepot/mybranch/data/generated/...
=write group * * -//mydepot/mybranch/data/Worlds/myworld/generated/...

Now I would like to apply this restriction for any *branch* under mydepot and any *world* under Worlds, could someone tell me the best way to do it?
I was thinking of using the following syntax:

=write group * * -//mydepot/.../data/generated/...
=write group * * -//mydepot/.../data/Worlds/.../generated/...

or even to have it applicable to any depot

=write group * * -//.../data/generated/...
=write group * * -//.../data/Worlds/.../generated/...

Would this be the proper syntax?


-Jonathan Wilson