Loading...
Helix SwarmHelix Swarm
Loading...

br04.html

  • //
  • guest/
  • hari_krishna_dara/
  • perforce/
  • faq/
  • br04.html #1
  • View
  • Commits
  • Open Download .zip Download (2 KB) 
  1. <html>
  2. <head>
  3. <title>The Branching Papers -- Perforce FAQs</title>
  4. <head>
  5. <body bgcolor=#ffffff>
  6. <font size=-2><b><a href="branching.html#br04">[INDEX]</a></b></font>
  7. <p>
  8. <b>
  9. Why is Perforce so brain-dead when it comes to branching renamed files?
  10. </b>
  11. <blockquote>
  12. There are definitely shortcomings in how Perforce handles renames across
  13. branches. First, it's difficult to explain (even though it's not that hard 
  14. to understand). Second, there's no automatic way to add a rename line to a
  15. branch spec -- you have to do it by hand, in a separate step from doing
  16. the rename.  And finally, branch specs are not versioned.  So if someone
  17. comes along and mangles the view in a branch spec, you have to do a
  18. bit of journal-pecking to get the old spec back.  (As a hedge, I
  19. recommend storing the "-o" outputs of important specs along with all
  20. other project files.)
  21. <p>
  22. However, despite these shortcomings, our current mechanism does seem to
  23. support some pretty sophisticated SCM. Some very big, very busy shops
  24. tell us they get a lot more mileage out of Perforce branching than they
  25. ever did out of any other system.
  26. <p>
  27. And there's hope -- atomic, persistent file renames, and versioned specs
  28. (client specs, branch specs, etc.), are both on the list of enhancements
  29. we hope to implement someday.
  30. </blockquote>
  31. <p>
  32. <i>(February 1999)</i>
  33. </p>
  34. <font size=-2><b><a href="branching.html#br04">[INDEX]</a></b></font>
  35.  
  36. <hr>
  37. <h6>This is file $Id: //guest/hari_krishna_dara/perforce/faq/br04.html#1 $ in the
  38. <a href="http://public.perforce.com/public/index.html">
  39. Perforce Public Depot</a></h6>
  40. </body>
  41. </html>
# Change User Description Committed
#1 5093 Hari Krishna Dara Populating perforce branch.
I will be adding p4admin files to it. 		20 years ago
//public/perforce/faq/br04.html
#1 112 Laura Wingerd Publish "Branching FAQ"
(pull in changes from //guest/laura_wingerd/perforce/faq/... ) 		26 years ago
//guest/laura_wingerd/perforce/faq/br04.html
#1 83 Laura Wingerd The Branching Papers. 26 years ago