On Fri, May 25, 2001 at 11:31:07AM -0400, Hamish Macdonald wrote:
I perform the following steps:
1) Delete the entire vendor tree (without telling Perforce)
2) Copy in new vendor release into the vendor tree in my workspace
3) do a "p4 add everything in the tree" using either the GUI or the
command line. This catches new files.
I have a scipt that selectively only adds actual new files (no real need to
do that as "p4 add already_existing_file" is innocuous) and skip CVS control
files and directories. This is handy when the "vendor" is a CVS tree. I
should extend the script to adhere to .cvsignore contents. I have attached my
script for anybody that may want to have the same (beware, it is slow on
large trees)
4) Use "p4 diff -se/p4 diff -sd" (or "Check Consistency" from the GUI)
to find the changed or deleted files.
5) submit (added, deleted, changed) ...
This seems to work well for me.
Trent
11 messages in com.perforce.perforce-user[p4] dry-run mode for edit, delete, a...