On 10/13/2015 08:15 AM, Tom Lane wrote:
Andres Freund <and...@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
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.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
