Dnia 25 lipca 2017 12:59:21 CEST, Tobias Klausmann <klaus...@gentoo.org>
napisał(a):
>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?
Yeah, i meant to apply the "must not" to wrapping but "should not" to length.
Though I suggest you to ellipsize the package name, if it is unambiguous enough.
The problem is that if you exceed the length, the summary will be usually cut
one way or another anyway.
>
>
>Regards,
>Tobias
>
>[0]
>$ cd /usr/portage
>$ ls -d *-*/*|awk '{if (length>=40) {print length, $0}}'|sort -n
--
Best regards,
Michał Górny (by phone)
