I saw David's response and had dealt with the same issue with "p4 add"ed files
that needed to be reviewed.
(Reference:
http://www.mail-archive.com/codestriker-user@lists.sourceforge.net/msg00037.html
So I decided to fix this issue for myself. Here's a github entry that might
help:
https://github
Hi Tom,
Yes, perforce diff unfortunately doesn't seem to create information for
added/removed files, which is incredibly annoying. If you are reviewing code
which has already been committed into the depot, then you can view
added/removed files from the changeset using the p4 describe command.
ay, July 08, 2005 10:38 AM
To: Tom Fenstermacher; codestriker-user@lists.sourceforge.net
Subject: Re: [Codestriker-user] code reviewing new files
Hi,
I have not used perforce before, so I don't know of any tricks to get
the perforce diff to do
this.
With the gnu diff, there is a
Hi,
I have not used perforce before, so I don't know of any tricks to get the
perforce diff to do
this.
With the gnu diff, there is an option -N
-N --new-file
Treat absent files as empty.
I looked up the perforce docs on its diff command and I did not see an
equivalent.
Title: code reviewing new files
Let me first start by saying that codestriker is an awesome tool. Many thanks to David and anyone else who has contributed to making it some helpful.
This tool has been very effective to enable the tracking of changes to existing files (i.e. 1 version already
