diff options
| author | c74d <8573dd@gmail.com> | 2018-10-10 21:06:12 +0000 |
|---|---|---|
| committer | c74d <8573dd@gmail.com> | 2018-10-10 21:06:12 +0000 |
| commit | e74c7666c7cb80fb48e65403b916ba775538cd0e (patch) | |
| tree | 35f0b7586410175941ca11be0c6dc8c29726991f /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch | |
| parent | adc6e9c2c4f4772defc36452e9aaf61da2e99cbc (diff) | |
CONTRIBUTING.md: Clarify clarification on periods
Commit 9428c28f7a37038b594c5ff36b1669b0f21afe41 added a note in
`CONTRIBUTING.md` saying that, "For consistency, there should not be a
period at the end of the commit message."
I believe it would be more correct (with respect to consistency) to
say that there should not be a full stop/period at the end of the
commit message's *summary line* (the first line of the commit message)
(indeed, the example commit message just above this note clearly does
use full stops outside of its summary line), and this patch changes
`CONTRIBUTING.md` accordingly.
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions