On Sat, Jan 24, 2009 at 10:42 AM, Bernie Innocenti wrote:
> Well, it's customary to introduce an additional state where the bug is
> fixed in the developer's intentions, but not yet QA'd:
>
> NEW -> ASSIGNED -> FIXED -> CLOSED
Bernie,
99% of my commits are "working on it, mate" ;-)
It's not ab
Martin Langhoff wrote:
> On Sat, Jan 24, 2009 at 6:39 AM, Bernie Innocenti wrote:
>> I meant it should have been optional, but if we switch to using the
>> "Closes: header in the body, where we have no size constraints, then
>> we could has well use the prefix consistently.
>
> One important note
On Sat, Jan 24, 2009 at 6:39 AM, Bernie Innocenti wrote:
> I meant it should have been optional, but if we switch to using the
> "Closes: header in the body, where we have no size constraints, then
> we could has well use the prefix consistently.
One important note WRT 'Closes'...
Code hits git
Jonas Smedegaard wrote:
>> - Given the above, the word "Closes: " steals precious characters,
>> and is rather easy to deduce, therefore I'd opt it out.
>
> It really makes better sense to me to not squeeze bug hints into that
> first line at all, but instead include them in a later line of the
On Fri, Jan 23, 2009 at 13:22, Simon Schampijer wrote:
> Marco Pesenti Gritti wrote:
>> On Fri, Jan 23, 2009 at 10:45 AM, Bernie Innocenti
>> wrote:
>>> Some thoughts:
>>>
>>> - Because the commit message summary appears in the shortlog,
>>> it should be kept below 74 characters to avoid ugly
Marco Pesenti Gritti wrote:
> On Fri, Jan 23, 2009 at 10:45 AM, Bernie Innocenti wrote:
>> Some thoughts:
>>
>> - Because the commit message summary appears in the shortlog,
>> it should be kept below 74 characters to avoid ugly wrapping.
>>
>> - Given the above, the word "Closes: " steals pre
