Loading...
Helix SwarmHelix Swarm
Loading...

p4History.html

  • //
  • guest/
  • mitch_stuart/
  • perforce/
  • utils/
  • delta/
  • doc/
  • p4History.html #1
  • View
  • Commits
  • Open Download .zip Download (3 KB) 
  1. <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
  2.  
  3. <!-- $Id: //guest/mitch_stuart/perforce/utils/delta/doc/p4History.html#1 $ -->
  4.  
  5. <html>
  6. <head>
  7. <link rel="stylesheet" type="text/css" href="styles.css" />   
  8. <title>p4History</title>
  9. </head>
  10. <body>
  11.  
  12. <h2>p4History</h2>
  13.  
  14. <h3>Introduction</h3>
  15. Perforce has commands that give the history of changes to a file, and other
  16. commands that give information on labels.  However, there is no single
  17. command that gives an "integrated" history, showing all of a file's changes and
  18. which labels match up with those changes.
  19.  
  20. <p />
  21. Having an integrated history is essential for understanding the changes
  22. that occurred between labels (that is, the changes between builds, releases,
  23. or other milestones that are labeled).
  24.  
  25. <p />
  26. The p4History.py  script displays the revision history of a file in reverse chronological
  27. order (like p4 changes or p4 filelog), but it also interleaves the labels
  28. (if any) applied to this file.  Normally you would have to invoke the
  29. p4 labels and p4 files commands separately to get all of this information.
  30.  
  31. <h3>Environment Requirements</h3>
  32. <ol>
  33. <li>This script invokes the Perforce p4 command-line interface to get the
  34. needed information from Perforce.  The p4 command must be available on your
  35. PATH, and you must have configured your environment so that the p4 command
  36. is able to access the Perforce server.</li>
  37.  
  38. <p />
  39. <li>You must have Python installed.  This script has been tested using Python 2.2.</li>
  40. </ol>
  41.  
  42.  
  43. <h3>Command Line Syntax</h3>
  44.  
  45. <code><pre>  p4History.py <i>filename</i></pre></code>
  46.  
  47.  
  48. <h3>Example</h3>  
  49. Sample invocation:
  50.  
  51. <code><pre>  p4History.py build.sh</pre></code>
  52.  
  53. Sample output:
  54.  
  55. <code><pre>
  56.   Label ducati-label-5: niranjan: 07/03/03 16:34: Created by niranjan.
  57.   Label suzuki-label-3: niranjan: 07/02/03 22:19: Created by niranjan.
  58.   Change 3913: mstuart: 07/01/03 16:03: Split StringMapper utility class into its own file
  59.   Change 3903: mstuart: 06/30/03 15:59: Implement migration from condenser.xml into database
  60.   Change 3890: krishna: 06/30/03 11:10: fixed a security bug w/ jboss
  61.   Change 3886: mstuart: 06/27/03 18:35: Compile JPull and JConsole with the same javac command, because they depend on each other.
  62.   Change 3863: krishna: 06/26/03 16:39: Added node type detection via node manager
  63.   Label suzuki-label-2: niranjan: 06/25/03 17:50: Created by niranjan.
  64.   Change 3851: krishna: 06/25/03 16:49: Build error with cp
  65.   Change 3823: krishna: 06/24/03 16:19: Product Separation project : another batch of changes
  66.   Change 3780: mstuart: 06/20/03 19:56: Add MBean meta info class
  67.   . . .
  68. </pre></code>
  69.  
  70. From the above output we can see that Change 3851 is included in
  71. suzuki-label-2, but Change 3863 is not.  This type of view helps to answer
  72. questions about which features and bug fixes appear in which releases.
  73.  
  74. </body>
  75. </html>
  76.  
# Change User Description Committed
#1 3652 Mitch Stuart Initial checkin 21 years ago