From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)anarazel(dot)de> |
Cc: | Álvaro Hernández Tortosa <aht(at)8Kdata(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: bugs and bug tracking |
Date: | 2015-10-13 15:39:16 |
Message-ID: | 561D25A4.8010801@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 10/13/2015 08:15 AM, Tom Lane wrote:
> Andres Freund <andres(at)anarazel(dot)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
>
> regards, tom lane
>
>
--
Command Prompt, Inc. - http://www.commandprompt.com/ 503-667-4564
PostgreSQL Centered full stack support, consulting and development.
New rule for social situations: "If you think to yourself not even
JD would say this..." Stop and shut your mouth. It's going to be bad.
From | Date | Subject | |
---|---|---|---|
Next Message | Michal Novotny | 2015-10-13 15:48:55 | Database schema diff |
Previous Message | Tom Lane | 2015-10-13 15:27:52 | Re: Postgres service stops when I kill client backend on Windows |