[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Commit header lines (was: git history tracking across renames (and e

From: Eli Zaretskii
Subject: Re: Commit header lines (was: git history tracking across renames (and emacs support))
Date: Sat, 14 Jul 2018 19:23:52 +0300

> Cc: address@hidden
> From: Paul Eggert <address@hidden>
> Date: Sat, 14 Jul 2018 11:09:27 -0500
> On 07/14/2018 01:58 AM, Eli Zaretskii wrote:
> > There are header lines that don't
> > add any information to the log message, in many cases they are just
> > the first entry slightly rephrased.
> If a summary line is a shorter version of the main text, that's a good
> thing. It's like a good title for a news article or a research paper: it
> restates the main text briefly, and there is real value in that.

I disagree with your perception, but I guess we are getting into the
gray area where personal preferences mean more than anything else.

> By the way, the usual suggested length limit for summary lines is 50
> characters, not 65.

50 is the suggested length, but 65 is the absolute maximum, mainly
because otherwise it will overflow the margin when we create a
ChangeLog out of Git log.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]