On Fri, Mar 17, 2017 at 10:00:17AM -0400, Tom Lane wrote: > Andrew Dunstan <andrew.duns...@2ndquadrant.com> writes: > > On 03/17/2017 09:30 AM, Robert Haas wrote: > >> In the department of nitpicks, we usually try to write commit messages > >> so that the first line is a summary line which stands alone, and then > >> there's a blank line, and then more follows. a la > >> https://chris.beams.io/posts/git-commit/#separate > > > Yeah, In our case email subjects seem to be truncated at 64 chars, so > > it's best to stay under that limit if possible - 50 chars is sometimes > > pretty limiting. > > FWIW, I usually try to keep line length in commit messages to <= 75 > characters, as that is the wrap boundary in "git log" output. It's > nice if the summary line can be made shorter, but it's often damn > hard to cram an adequate summary into 75 chars, let alone fewer. > > (Links to mailing-list threads must ignore the length limit, sadly.)
Here are the length limits I have found, and I display this in my email editor when I am creating a commit message: -- email subject limit ----------------------------------------- -- gitweb summary limit -------------------------- -- Bruce Momjian <br...@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Ancient Roman grave inscription + -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
