On Tue, Oct 13, 2015 at 08:39:16AM -0700, Joshua Drake wrote: > On 10/13/2015 08:15 AM, Tom Lane wrote: > >Andres Freund <and...@anarazel.de> writes: > >>On 2015-10-13 16:21:54 +0200, �lvaro Hern�ndez Tortosa wrote: > >>>(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. > > > >I agree --- I have a hard enough time writing a good summary in 75 > >characters. 50 would be awful. > > The idea of writing a commit message that is useful in a number of > characters that is less than half a tweet sounds unbearable. The > idea of trying to discern what the hell a commit actually is in a > number of characters that is less than half a tweet sounds > completely ridiculous. > > -1 on that particular aspect.
FYI, I think we already have two limits for the first line summary of commit messages. The limits are 64 for commit message subjects and 50 characters for gitweb summary pages --- anything longer is truncated. My commit template shows me the limits as I am typing the commit text to remind me of the limits: -- 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. + + Roman grave inscription + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
