On 10/01/15 18:03, Eric Blake wrote:
[meta-comment]
On 10/01/2015 06:14 AM, Marc Marí wrote:
Implementation of the FW CFG DMA interface.
The subject line is missing "v4" and "0/7". Also, the cover letter is missing a diffstat. That makes it harder to see from the cover letter what the rest of the series is about. 'git format-patch/send-email --cover-letter' does what you want; you can even 'git config format.coverletter=auto' to always include a decent cover letter on any multi-patch series.
This posting follows a little bit different pattern, one that I myself follow when posting patches for two (or more) components that must work in sync.
Usually, a top-level blurb is manually cross-posted to all relevant mailing lists. Then, each separate patch series is posted only to the relevant mailing list, with its own cover letter (as usual with git), *in response* to the manually posted blurb.
This has the following benefits:
- in mailing list archives that organize messages into threads *across* mailing lists (like Gmane does, for example), the top-level manual blurb is a good "root" for referencing the entire posting.
- The same is true for personal mailboxes, if a recipient is explicitly CC'd on all of the messages.
Because the top level blurb is parent to several patch series, and those child series can all have different version numbers (due to different numbers of respinds), it is not always straightforward to assign a version number to the top blurb.
Thanks Laszlo