[p4] Detecting files that were modified but not checked out
Melissa Kacher
mkacher at intrinsyc.com
Fri May 19 12:10:18 PDT 2006
C:\>p4 help diff
diff -- Display diff of client file with depot file
p4 diff [ -d<flag> -f -sa -sd -se -sr -t ] [ file[rev] ... ]
Run diff (on the client) of a client file against the
corresponding
revision in the depot. The file is only compared if the file is
opened for edit or the revision provided with the file argument
is
not the same as the revision had by the client. See 'p4 help
revisions' for help specifying revisions.
If no file argument is given, diff all open files.
This can be used to view pending changelists.
The -d<flag> passes a flag to the built-in diff routine to
modify
the output: -dn (RCS), -dc (context), -ds (summary), -du
(unified),
-db (ignore whitespace changes), -dw (ignore whitespace),
-dl (ignore line endings).
The -f flag forces a diff for every file, regardless of whether
they are opened or if the client has the named revision.
This can be used to verify the client contents.
The -s flag reduces the output of diff to the names of files
satisfying one of the following criteria:
-sa Opened files that are different from the
revision
in the depot, or missing.
-sd Unopened files that are missing on the client.
------->>>> -se Unopened files that are different from the revision
in the depot.
-sr Opened files that are the same as the revision
in the
depot.
The -t flag forces 'p4 diff' to diff even files with non-text
(binary) types.
If the environment variable $P4DIFF is set then the named
program is
used rather than the implementation of diff included in the
client.
The -d<flag>command can be used to pass arguments to the
external
program. The -s flag is only implemented internally.
The environment variable $P4DIFFUNICODE is used instead of
$P4DIFF
if the file being diffed is of a unicode type and the character
set is passed as the first argument to that command.
Thanks,
Melissa
-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Edil Cadenas
Sent: Friday, May 19, 2006 10:07 AM
To: perforce-user at perforce.com
Subject: [p4] Detecting files that were modified but not checked out
Does anyone know if there is a way to find all files in the workspace
that have been modified without being checked out? We use certain
scripts that require files to be modified without being checked out so
what our users do is to change the attributes of workspace files to
writeable.
In VSS, there is a tool to find these files that were modified but were
not checked out. ClearCase also detects these files. Does anyone know
if such functionality also exists in Perforce?
With much thanks,
Edil Cadenas
_______________________________________________
perforce-user mailing list - perforce-user at perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user
More information about the perforce-user
mailing list