<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Sep 24, 2014, at 16:08, Renato Golin <<a href="mailto:renato.golin@linaro.org" class="">renato.golin@linaro.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">On 25 September 2014 00:03, Tim Northover <<a href="mailto:t.p.northover@gmail.com" class="">t.p.northover@gmail.com</a>> wrote:<br class=""><blockquote type="cite" class="">I tend to follow something like that anyway so I think it's a good<br class="">idea, but if anything I'd prefer a longer title line than the body.<br class="">Particularly with the prefixes we tend to put in there, 50 chars is<br class="">hardly anything.<br class=""></blockquote><br class="">I only mentioned 50-col because that's what Vim helps me do automatically. :)<br class=""><br class="">I'm fine with larger titles, but not larger than 70-col, which should<br class="">be plenty, since we don't have complex branching in git. GMail can<br class="">cope with up to 90 chars (+preamble) in the subject.<br class=""></div></blockquote></div><br class=""><div class="">I try to wrap summaries at 80 columns by hand (so as to make reading logs in a shell easier) but even 70 columns is short with "[analyzer] " at the front. I'm okay with picking a length as a target; I just don't want us to start sending complaints to people whose first lines go over the limit.</div><div class=""><br class=""></div><div class="">(Now, people whose summary "line" is broken up into multiple lines, sure, because that affects e-mail <i class="">and</i> git (and SVN these days? not sure).</div><div class=""><br class=""></div><div class="">Jordan</div></body></html>