| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Commit subject line |
| Date: | 2013-05-03 18:43:09 |
| Message-ID: | 28870.1367606589@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> writes:
> On 03.05.2013 20:56, Bruce Momjian wrote:
>> On Fri, May 3, 2013 at 01:42:33PM -0400, Andrew Dunstan wrote:
>>> Yeah. The recommended style is to have the first line be 50 chars or
>>> less, which is a bit unfortunate - it can be a challenge to keep to
>>> that limit for a meaningful or comprehensive subject.
> Oh, that's tight. I didn't know about the 50 char recommendation. I've
> tried to keep mine < 76 chars, so that when you do "git log", it fits on
> a 80 char display with the 4 char indentation that git log does.
Yeah, that's news to me too. I've been using a 75-char line length for
all my commit messages since we switched to git. It's frequently tough
enough to get a useful headline into 75 chars --- I can't see trying to
do 50.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2013-05-03 18:43:38 | Re: Commit subject line |
| Previous Message | Jeff Janes | 2013-05-03 18:42:05 | Re: pg_ctl idempotent item removed |