On 18/11/2021 01:34, Vincent Pelletier wrote: > On Wed, 17 Nov 2021 10:28:59 +0100, Krzysztof Kozlowski <krzysztof.kozlowski@xxxxxxxxxxxxx> 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@xxxxxxxxx> >>> >>> -- >>> 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. There is an idea of git notes (wasn't really efficient) or git branch description for cover letter (--cover-from-description, didn't try yet). > > 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) ? There are few different options, so depends what do you want, e.g.: git send-email --cc-cmd "scripts/get_maintainer.pl --no-git --no-roles --no-rolestats" --to linux-kernel@xxxxxxxxxxxxxxx 0* However above does not take care about cover-letter. > > 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 ? Not sure. Anyway just look at the lists at lore.kernel.org how other people are doing it. Best regards, Krzysztof
