Loading...
Helix SwarmHelix Swarm
Loading...

p4.html

  • //
  • guest/
  • timothee_besset/
  • docs/
  • html/
  • VCP/
  • Dest/
  • p4.html #1
  • View
  • Commits
  • Open Download .zip Download (3 KB) 
  1. <html><head><title>VCP::Dest::p4 - p4 destination driver</title></head><body><h1><a name="NAME">NAME
  2.  
  3. </a></h1><p>VCP::Dest::p4 - p4 destination driver
  4.  
  5. <p><hr><h1><a name="SYNOPSIS">SYNOPSIS
  6.  
  7. </a></h1><pre>   vcp &lt;source&gt; p4:user:password@p4port:[&lt;dest&gt;]
  8.    vcp &lt;source&gt; p4:user(client):password@p4port:[&lt;dest&gt;]
  9.    vcp &lt;source&gt; p4:[&lt;dest&gt;]
  10.  
  11. </pre><p>The &lt;dest&gt; spec is a perforce repository spec and must begin with // and a
  12. depot name (&quot;//depot&quot;), not a local filesystem spec or a client spec. There
  13. should be a trailing &quot;/...&quot; specified.
  14.  
  15. <p>If no user name, password, or port are given, the underlying p4 command will
  16. look at that standard environment variables. The password is passed using the
  17. environment variable P4PASSWD so it won't be logged in debugging or error
  18. messages, the other options are passed on the command line.
  19.  
  20. <p>If no client name is given, a temporary client name like &quot;vcp_tmp_1234&quot; will be
  21. created and used.  The P4CLIENT environment variable will not be used.  If an
  22. existing client name is given, the named client spec will be saved off,
  23. altered, used, and restored.  the client was created for this import, it will
  24. be deleted when complete, regardless of whether the client was specified by the
  25. user or was randomly generated.  WARNING: If perl coredumps or is killed with a
  26. signal that prevents cleanup--like a SIGKILL (9)--the the client deletion or
  27. restoral will not occur. The client view is not saved on disk, either, so back
  28. it up manually if you care.
  29.  
  30. <p>THE CLIENT SAVE/RESTORE FEATURE IS EXPERIMENTAL AND MAY CHANGE BASED ON USER
  31. FEEDBACK.
  32.  
  33. <p>VCP::Dest::p4 attempts change set aggregation by sorting incoming revisions.
  34. See <a>VCP::Dest/rev_cmp_sub</a> for the order in which revisions are sorted. Once
  35. sorted, a change is submitted whenever the change number (if present) changes,
  36. the comment (if present) changes, or a new rev of a file with the same name as
  37. a revision that's pending. THIS IS EXPERIMENTAL, PLEASE DOUBLE CHECK
  38. EVERYTHING!
  39.  
  40. <p><hr><h1><a name="DESCRIPTION">DESCRIPTION
  41.  
  42. </a></h1><p><hr><h1><a name="METHODS">METHODS
  43.  
  44. </a></h1><dl><dt><a name="new_"><strong><p>new
  45.  
  46. </strong></a><dd>Creates a new instance of a VCP::Dest::p4.  Contacts the p4d using the p4
  47. command and gets some initial information ('p4 info' and 'p4 labels').
  48.  
  49. </dl><p><hr><h1><a name="AUTHOR">AUTHOR
  50.  
  51. </a></h1><p>Barrie Slaymaker &lt;barries@slaysys.com&gt;
  52.  
  53. <p><hr><h1><a name="COPYRIGHT">COPYRIGHT
  54.  
  55. </a></h1><p>Copyright (c) 2000, 2001, 2002 Perforce Software, Inc.
  56. All rights reserved.
  57.  
  58. <p>See <a href="../License.html">VCP::License</a> (<code>vcp help license</code>) for the terms of use.
  59.  
  60. <p><hr><i><font size="-1">Last updated: Fri Nov  8 13:07:22 2002</font></i></body></html>
# Change User Description Committed
#1 4040 timothee_besset guest branch 21 years ago
//guest/perforce_software/revml/docs/html/VCP/Dest/p4.html
#2 2307 Barrie Slaymaker get VCP::Filter::map working, update docs 22 years ago
#1 1993 Barrie Slaymaker Check in HTML documentation 23 years ago