<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Perforce on Pesches Schlauch</title>
    <link>https://pesche.schlau.ch/tags/perforce/</link>
    <description>Recent content in Perforce on Pesches Schlauch</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Tue, 03 Jul 2007 17:06:15 +0200</lastBuildDate>
    <atom:link href="https://pesche.schlau.ch/tags/perforce/feed.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Merge down, copy up</title>
      <link>https://pesche.schlau.ch/2007/07/03/merge-down-copy-up/</link>
      <pubDate>Tue, 03 Jul 2007 17:06:15 +0200</pubDate>
      <guid>https://pesche.schlau.ch/2007/07/03/merge-down-copy-up/</guid>
      <description>&lt;p&gt;If you are using any SCM that allows cheap branches (like &lt;a href=&#34;http://www.perforce.com/&#34;&gt;Perforce&lt;/a&gt;) and are following the advices from the &lt;a href=&#34;http://www.perforce.com/perforce/bestpractices.html&#34;&gt;High-level Best Practices&lt;/a&gt; document, you might be interested in (or already know) Laura Wingerd&#39;s presentation &lt;a href=&#34;http://www.perforce.com/perforce/conferences/eu/2006/presentations/laura_wingerd/ConvergenceVsDivergence.html&#34;&gt;Convergence vs. Divergence: Purposeful Merging with Perforce&lt;/a&gt; about how to converge to codelines using &lt;a href=&#34;http://www.perforce.com/perforce/conferences/us/2005/presentations/Wingerd.pdf&#34;&gt;Merge Down, Copy Up [PDF]&lt;/a&gt;. I have seen it many times that a main codeline got broken because the Merge Down, Copy Up idiom was ignored.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
