<div class="gmail_quote">On Fri, Aug 3, 2012 at 7:15 PM, Richard Fontana <span dir="ltr">&lt;<a href="mailto:fontana@sharpeleven.org" target="_blank">fontana@sharpeleven.org</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On 08/03/2012 09:09 AM, Bradley M. Kuhn wrote:<br>
</div><div class="im">&gt; Anyway, the merge request is:<br>
&gt; <a href="https://gitorious.org/copyleft-next/copyleft-next/merge_requests/10" target="_blank">https://gitorious.org/copyleft-next/copyleft-next/merge_requests/10</a><br>
<br>
</div>I have rejected this patch, though I&#39;ve adapted some of your general<br>
modifications to the &#39;Corresponding Source&#39; definition.<br>
<br>
<a href="https://gitorious.org/copyleft-next/copyleft-next/commit/2457a57bda65bc42ae16faea50fe6a72a7ccb25f" target="_blank">https://gitorious.org/copyleft-next/copyleft-next/commit/2457a57bda65bc42ae16faea50fe6a72a7ccb25f</a><br>

<span class="HOEnZb"></span></blockquote><div><br>That should be &quot;any scripts...&quot; not just &quot;scripts&quot;, no? <br><br>Also, I&#39;ve never been sure what &quot;control&quot; means in this context. Given that &quot;perform&quot; is probably broad enough to completely encompass &quot;control,&quot; and given how comprehensive the list of tasks is now (it&#39;s arguably impossible to &quot;perform&quot; a build without some form of control) I&#39;d be inclined to replace &quot;control and perform&quot; with simply &quot;perform,&quot; or else give a more specific definition of &quot;control&quot; (e.g, by reference to configuration files.)<br>
<br>Luis<br></div></div>