On Tue 2016-08-30 04:55:19 -0400, Laurent Bercot wrote: > Please avoid sending patches to this list with git-send-email, or at > least please provide a 0/n introductory message to give context. This > list is read by humans.
I'm a human, and i read this list :) I will be happy to send a 0/n introductory message (git send-email --compose) for any future proposed series, i was not aware that was the custom here. Indeed, i wrote this series because i could find no clear instructions for how to propose improvements to runit's codebase. This series is a set of minor changes to improve the web presence for runit and to make it clearer how to contribute code. Alternately, if there's a better way to propose changes than sending mail to this list, i'd be happy to rewrite code.html to document it, but i don't know what it is. Perhaps an additional patch to the proposed doc/code.html to add the --compose argument to git send-email would make that clearer. If i were to do that, would you prefer i send a new series of patches (rebased against master so that they apply directly) or a new follow-on patch to this series ("4/3", as it were) that just adds the --compose argument to the example of how to send patches? regards, --dkg
signature.asc
Description: PGP signature