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

From Álvaro Hernández Tortosa
Subject Re: bugs and bug tracking
Date
Msg-id 561D1382.2020806@8Kdata.com
Whole thread Raw
In response to Re: bugs and bug tracking  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: bugs and bug tracking  (Andres Freund <andres@anarazel.de>)
Re: bugs and bug tracking  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
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)
    Álvaro


-- 
Álvaro Hernández Tortosa


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




pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: bugs and bug tracking
Next
From: Andres Freund
Date:
Subject: Re: bugs and bug tracking