[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 09:58:50 +0300

> From: Richard Stallman <address@hidden>
> Date: Fri, 13 Jul 2018 19:11:26 -0400
> Cc: address@hidden, address@hidden, address@hidden, address@hidden,
>       address@hidden
>   > The two I found less useful were
>   > "Unbreak bootstrap" (a motivation for the change, but not enough
>   > description) and "Fix Bug#32107" (likewise). It'd be helpful for us to
>   > encourage people to write commit messages with summary lines that are
>   > suitable for later readers.
> I agree.

Unfortunately, the percent of the "less useful" summary lines I see is
significantly larger than 2 in 10.  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.  In other cases, they say
something uninformative like "Minor copyedits SOMEWHERE".  And in
many/most of those cases I see no better way to phrase the header line
that would fit into 65 characters.  (Some of those header lines are
mine, btw, which means it's already the best wording I could come up

Again, it's a minor gripe, and a little price to pay.  But let's not
forget that a price it is.

reply via email to

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