<div class="gmail_quote">On Fri, Aug 3, 2012 at 7:15 PM, Richard Fontana <span dir="ltr"><<a href="mailto:fontana@sharpeleven.org" target="_blank">fontana@sharpeleven.org</a>></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">> Anyway, the merge request is:<br>
> <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've adapted some of your general<br>
modifications to the 'Corresponding Source' 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 "any scripts..." not just "scripts", no? <br><br>Also, I've never been sure what "control" means in this context. Given that "perform" is probably broad enough to completely encompass "control," and given how comprehensive the list of tasks is now (it's arguably impossible to "perform" a build without some form of control) I'd be inclined to replace "control and perform" with simply "perform," or else give a more specific definition of "control" (e.g, by reference to configuration files.)<br>
<br>Luis<br></div></div>