Hi!
On Tue, 25 Jul 2017, Michał Górny wrote:
> The summary line is included in the short logs (<kbd>git log --
> oneline</kbd>, gitweb, GitHub, mail subject) and therefore should
> provide a short yet accurate description of the change. The summary line
> starts with a logical unit name, followed by a colon, a space and a
> short description of the most important changes. If a bug is associated
> with a change, then it should be included in the summary line as
> <kbd>#nnnnnn</kbd> or likewise. The summary line must not exceed 69
> characters, and must not be wrapped.
This limit can be a problem if there's a nontrivial change to the
more than 80 packages in the tree that have more than forty characters in
cat/pkg[0]. Is the only option there to do word-smithing or
making the commit summary less usefu?
Or do we have a "violate if necessary" agreement regarding that?
Regards,
Tobias
[0]
$ cd /usr/portage
$ ls -d *-*/*|awk '{if (length>=40) {print length, $0}}'|sort -n
--
Sent from aboard the Culture ship
GSV Of Course I Still Love You
