Messages in this thread | | | Date | Thu, 18 Nov 2021 00:34:18 +0000 | From | Vincent Pelletier <> | Subject | Re: [PATCH v2 1/6] riscv: dts: sifive unmatched: Name gpio lines |
| |
On Wed, 17 Nov 2021 10:28:59 +0100, Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com> wrote: > On 17/11/2021 00:57, Vincent Pelletier wrote: > > Follow the pin descriptions given in the version 3 of the board schematics. > > > > Signed-off-by: Vincent Pelletier <plr.vincent@gmail.com> > > > > -- > > Changes since v1: > > - Remove trailing "." on subject line. > > --- > > This is not a correct changelog placement - you have to use '---' just > like git uses it. Just test it yourself and you will see the problem.
Indeed, thanks for catching this.
Is there a recommended way for managing these not-for-commit-message chunks automatically ? I obviously compose them by hand so far, and put them in my local git working copy commit messages, but I would be happier if I did not have to make (bad) decisions on such mechanical detail.
On a related topic, is there a way to automate "git send-email" recipient list using get_maintainer.pl (plus some more magic lines, for example to exclude bouncing addresses) ?
While process/submitting-patches.rst describes what the result should look like, it feels to me that it (or another related file) could be more directive on what commands/workflows help to get such result, for casual contributors like myself. Have I missed such documentation ?
Regards, -- Vincent Pelletier GPG fingerprint 983A E8B7 3B91 1598 7A92 3845 CAC9 3691 4257 B0C1
| |