<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Thu, Jul 17, 2014 at 10:19 AM, Frank Loeffler <span dir="ltr"><<a href="mailto:knarf@cct.lsu.edu" target="_blank">knarf@cct.lsu.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">We could provide one. We cannot enforce people installing it.<br>
<div class=""><br>
> and on top of that set up the server to reject unformatted messages?<br>
<br>
</div>That is probably the better option. Although I would only see it as help<br>
to "not forget about it", not an enforcement really (although<br>
technically it is the same). We cannot disallow anything else than thorn<br>
names before the ":" (we might have commit touching multiple thorns), so<br>
we cannot technically prevent something like "somewhere: changed<br>
something". But we don't need to technically enforce everything anyway.</blockquote><div><br></div><div>This is a good point. While it seems like a good general guideline to have the thorn name as a prefix in any commit message, I'm not convinced it is a good idea to strictly enforce it. For example, what about commits that modify several thorns at once?</div>
<div><br></div><div>Carpet has a policy like this; in general commit messages are prefixed by the thorn name, but occasionally there will be a message which changes many thorns at once and doesn't adhere to this convention.</div>
</div></div></div>