Re: bugs and bug tracking

From: Álvaro Hernández Tortosa <aht(at)8Kdata(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: bugs and bug tracking
Date: 2015-10-13 14:21:54
Message-ID: 561D1382.2020806@8Kdata.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2015-10-13 14:24:35 Re: bugs and bug tracking
Previous Message Magnus Hagander 2015-10-13 14:11:29 Re: bugs and bug tracking