<div dir="ltr">On Wed, Aug 13, 2008 at 5:55 PM, Yuval Hager <span dir="ltr"><<a href="mailto:yuval@avramzon.net">yuval@avramzon.net</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Wednesday 13 August 2008, Nathaniel Catchpole wrote:<br>
> So if you already have HEAD installed (I pretty much only clean my<br>
> database before or after reviewing a patch with an upgrade path or<br>
> schema change), you can do this:<br>
><br>
> // clean your HEAD of old changes.<br>
> cvs -q diff | patch -p0 -R<br>
><br>
> wget <a href="http://drupal.org/files/issues/somepatch.patch" target="_blank">http://drupal.org/files/issues/somepatch.patch</a><br>
><br>
> patch -p0 < somepatch.patch<br>
><br>
> 1 out of 1 hunks failed etc.<br>
><br>
> Mark to code needs work with 'needs a re-roll'.<br>
<br>
</div>Can't this process be automated? I think I remember something about a process<br>
that scans for stale patches - does it still exist?. The<br>
close-fixed-after-two-weeks bot seems to be doing a very nice work!<font color="#888888"><br></font></blockquote></div><br clear="all">This is supposed to go here at some point <a href="http://testing.drupal.org/">http://testing.drupal.org/</a><br>
-- <br>Khalid M. Baheyeldin<br><a href="http://2bits.com">2bits.com</a>, Inc.<br><a href="http://2bits.com">http://2bits.com</a><br>Drupal optimization, development, customization and consulting.<br>
</div>