Re: bugs and bug tracking - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: bugs and bug tracking
Date
Msg-id 561D197A.6040306@dunslane.net
Whole thread Raw
In response to Re: bugs and bug tracking  (Álvaro Hernández Tortosa <aht@8Kdata.com>)
List pgsql-hackers

On 10/13/2015 10:21 AM, Álvaro Hernández Tortosa wrote:
>
> On 13/10/15 04:40, Tom Lane wrote:
>> I'm with Robert on the idea that commit log entries need to be 
>> limited-width. I personally format them to 75 characters, so that 
>> git_changelog's output is less than 80 characters. regards, tom lane 
>
>     Little bit off-topic, but if precisely if we're trying to make the 
> commits/bug-tracking/whatever system more user-friendly also for 
> non-hacker users, I'd adhere to the 50/72 "standard" for commit 
> messages, which seems to be quite extended: 
> http://chris.beams.io/posts/git-commit/#seven-rules
>
> (50 chars for the commit summary, 72 chars line wrapping)
>
>


50 is a pretty short for a commit summary. I've often found it quite 
difficult to write sane summaries inside that limit.

cheers

andrew




pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: bugs and bug tracking
Next
From: Álvaro Hernández Tortosa
Date:
Subject: Re: bugs and bug tracking