Re: Template for commit messages

From: "Greg Sabino Mullane" <greg(at)turnstep(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Template for commit messages
Date: 2016-02-01 15:43:00
Message-ID: 02d47d129e4d35bb86dda9024334ccf8@biglumber.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

FWIW, I read the git logs quite a bit, especially after a release to
gather some stats, and I *love* the commits that have some nice
standard, easy to read fields (Alvaro for one does a great job
at this). I don't think we need to mandate it, or even ensure they
are machine-parseable, but I would like to see a few fields encouraged.
I think it also helps the committers to not forget some important
things, the way the free-form text can.

tl;dr be like Alvaro, please

- --
Greg Sabino Mullane greg(at)turnstep(dot)com
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201602011037
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----

iEYEAREDAAYFAlavfNwACgkQvJuQZxSWSsg4YgCgmWoL38qljypgUn082aWVp4y8
WDsAn24IwFKwqaudYRF1e3rvd0yz5btw
=2Jc2
-----END PGP SIGNATURE-----

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2016-02-01 15:49:46 Re: silent data loss with ext4 / all current versions
Previous Message Jim Nasby 2016-02-01 15:03:35 Re: Trigger.sgml