<?xml version="1.0"?>
<!DOCTYPE content [ <!ENTITY nbsp " "> ]>
<rdf:RDF xml:base="http://snarfed.org/rdf"
         xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
         xmlns:dc="http://purl.org/dc/elements/1.1/">

<rdf:Description rdf:about="http://snarfed.org">
  <dc:title> snarfed.org  </dc:title>
  <dc:description> draw group stream of consciousness </dc:description>
  <dc:creator> Ryan Barrett &lt;snarfed at ryanb dot org&gt; </dc:creator>
  <dc:language> en </dc:language>
  <dc:format> text/html </dc:format>
  <dc:rights> Copyright 2002-2007 Ryan Barrett </dc:rights>
</rdf:Description>

<rdf:Description rdf:about="http://snarfed.org/space/port_pine_patch">
  <dc:title> port_pine_patch </dc:title>
  <dc:creator> Ryan Barrett &lt;snarfed at ryanb dot org&gt; </dc:creator>
  <dc:date> 2003-01-01T05:00:00Z </dc:date>
  <dc:language> en </dc:language>
  <dc:format> text/html </dc:format>
  <dc:rights> Copyright 2002-2007 Ryan Barrett </dc:rights>

  <content>
    <p><a href="http://washington.edu/pine/"><img src="/space/pine.png" alt="pine.png" title="" /></a></p>

<p>For the impatient: <br />
<a href="/space/port_pine_patch.sh">Download port_pine_patch.sh v0.1</a> <br />
<a href="http://www.washington.edu/pine/getpine/unix.html">Pine source</a> <br />
<a href="/space/software#patches">My pine patches</a> <br />
<a href="http://www.math.washington.edu/~chappa/pine/faq/index.html">FAQ on patching
pine</a></p>

<p>I've written a number of <a href="/space/software#patches">patches</a> for
<a href="http://www.washington.edu/pine/">Pine</a>, my email client. For a while, I ported
them to new versions of Pine manually, which was very time consuming.</p>

<p>This shell script automates the task of porting patches between Pine versions.
It doesn't automatically resolve conflicts, but it does pretty much everything
else. Upgrading Pine with patches has never been easier! (Uh, maybe.)</p>

<p>To use the script to port a patch (on *nix!), first unpack the new version's
<a href="http://www.washington.edu/pine/getpine/unix.html">source</a> into your home
directory. The script will look for an existing patch for the old version in
<strong>~/src/pine</strong>, and will write out the new patch to the same directory. For
example, use this command line to port <strong>foo.patch.4.63</strong> to Pine version 4.64:</p>

<div class='p-shadow'><pre><code>./port_pine_patch.sh foo 4.63 4.64
</code></pre></div>

<p><br class='clearing' />Future versions will remove the hard-coded paths. For now, you can edit the
variables at the top of the script to point to different paths.</p>

<p>port_pine_patch is copyright 2005 <a href="http://ryan.barrett.name/">Ryan Barrett</a>,
and is distributed under the <a href="http://www.gnu.org/licenses/gpl.html">GPL</a>.</p>

<p>See also:</p>

<ul>
<li><a href="/space/pine delete attachments on save patch">pine delete attachments on save patch</a></li>
<li><a href="/space/pine flowed-text patch">pine flowed-text patch</a></li>
<li><a href="/space/pine remove trailing quote patch">pine remove trailing quote patch</a></li>
<li><a href="/space/pine reply-all patch">pine reply-all patch</a></li>
<li><a href="/space/gmail vs pine">gmail vs pine</a></li>
</ul>

  </content>

  <rdf:Seq>

  </rdf:Seq>
</rdf:Description>
</rdf:RDF>
