<div dir="ltr">Sounds good to me. <div><br></div><div>Thanks, James.</div><div><br></div><div><Zoltan></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Apr 4, 2014 at 2:51 PM, James Craig <span dir="ltr"><<a href="mailto:jcraig@apple.com" target="_blank">jcraig@apple.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On Apr 4, 2014, at 1:33 PM, Zoltan Horvath <<a href="mailto:zoltan@webkit.org">zoltan@webkit.org</a>> wrote:<br>
<br>
> On Fri, Apr 4, 2014 at 12:43 PM, James Craig <<a href="mailto:jcraig@apple.com">jcraig@apple.com</a>> wrote:<br>
><br>
>> On Apr 4, 2014, at 9:08 AM, Zoltan Horvath <<a href="mailto:zoltan@webkit.org">zoltan@webkit.org</a>> wrote:<br>
>><br>
>>> Hi there,<br>
>>><br>
>>> prepare-Changelog:<br>
>>> - The style checker script runs on the ChangeLogs as well, and it gives warning if the bug number or the tests' line are not filled.<br>
>><br>
>> I consider this an expected behavior. If you don't include --bug=12345 parameter when running prepare-Changelog, your diff is currently in a state that would fail style checks. Having the Terminal output immediately tell you that detail is useful.<br>
>><br>
>>> - I think the best behavior for this case would be to abort the change log creation, if there are errors on the actual code check. (Then you can fix those, and when you rerun prepare-Changelog, it puts the recent things into the change log. [e.g. you've got a lower/uppercase function naming warning, and the function name appears in the change log])<br>
>><br>
>> I don't think this is right. If we aborted the change log creation, you'd never be able to run prepare-Changelog without the --bug parameter, unless you specifically disabled the style check with --no-style.<br>
><br>
> I'd avoid running the style-checker on the change logs themselves <since these're being created> when running prepare-Changelog, and abort changelog creation, if the _rest of the code_ have coding style violation <since fact of violation is our interest at this point>.<br>
<br>
</div></div>What if we file another bug for that part of the work? It seems like a nice-to-have, but not necessary for this patch.<br>
</blockquote></div><br></div>