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

From Andres Freund
Subject Re: bugs and bug tracking
Date
Msg-id 20151013142435.GH10323@awork2.anarazel.de
Whole thread Raw
In response to Re: bugs and bug tracking  (Álvaro Hernández Tortosa <aht@8Kdata.com>)
Responses Re: bugs and bug tracking  (Álvaro Hernández Tortosa <aht@8Kdata.com>)
Re: bugs and bug tracking  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 2015-10-13 16:21:54 +0200, Á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)

-1 - imo 50 chars too often makes the commit summary too unspecific,
requiring to read much more.

Greetings,

Andres Freund



pgsql-hackers by date:

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