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