Re: bugs and bug tracking

On 13/10/15 17:39, Joshua D. Drake wrote:
> On 10/13/2015 08:15 AM, Tom Lane wrote:
>> Andres Freund <andres@anarazel.de> writes:
>>> On 2015-10-13 16:21:54 +0200, �lvaro Hern�ndez Tortosa wrote:
>>>> (50 chars for the commit summary, 72 chars line wrapping)
>>
>>> -1 - imo 50 chars too often makes the commit summary too unspecific,
>>> requiring to read much more.
>>
>> I agree --- I have a hard enough time writing a good summary in 75
>> characters.  50 would be awful.
>
> The idea of writing a commit message that is useful in a number of 
> characters that is less than half a tweet sounds unbearable. The idea 
> of trying to discern what the hell a commit actually is in a number of 
> characters that is less than half a tweet sounds completely ridiculous.
>
> -1 on that particular aspect.
>
> jD
>
    I'm writing a YC application and they ask you to summarize your 
whole project idea in less than 50 chars. So I guess that a commit 
message can be summarized under 50 chars too ^_^
We even do this with Java commits, and hey, you know, if you include a 
JavaStyleCamelCaseUnnecesarilyVerboseClassName in this summary you're 
screwed up!
    But it seems there's clear agreement on *not* restricting it to 50, 
so I have nothing else to add :)
    Best,
    Álvaro

-- 
Álvaro Hernández Tortosa


-----------
8Kdata