To be honest, I think git-publish is really lacking some major features. For example, there is no way to add per-commit changelogs “below the fold” (other than editing the emails manually). There’s also no way to CC people on individual patches, which is very helpful on larger series touching several subsystems where only some patches are relevant to particular people (although maybe CC: in the commit message works?). I do like the auto-tagging. I almost never tag a branch which means digging around in reflog if I forget what I changed.
Now FWIW I definitely won’t be using pyonji, since as far as I can tell the readme is the only documentation!
I don’t use any tool, I edit everything manually :D
For example, there is no way to add per-commit changelogs “below the fold” (other than editing the emails manually).
I think git-notes would show up below the fold but I haven’t done it before
There’s also no way to CC people on individual patches, which is very helpful on larger series touching several subsystems where only some patches are relevant to particular people
See [sendemail.cccmd] git setting, when you git-send-email it passes each patch file to this command and whatever it returns is added to the CC list.
I select recipients manually. get_maintainer is nice, and produces good suggestions, but it frequenty suggests too many people. For example, if you do a find/replace style commit which touches a lot of files, get_maintainer will suggest CCing you for a few years.
Nice tool!
For a mature, and more featured alternative you can also look at git-publish https://github.com/stefanha/git-publish
It also has the neat feature of not using golang. :^)
see also: patman and b4. If you’re curious what patman input/output looks like, here are the git commits for a series I recently sent. I don’t personally use b4.
To be honest, I think git-publish is really lacking some major features. For example, there is no way to add per-commit changelogs “below the fold” (other than editing the emails manually). There’s also no way to CC people on individual patches, which is very helpful on larger series touching several subsystems where only some patches are relevant to particular people (although maybe CC: in the commit message works?). I do like the auto-tagging. I almost never tag a branch which means digging around in reflog if I forget what I changed.
Now FWIW I definitely won’t be using pyonji, since as far as I can tell the readme is the only documentation!
I don’t use any tool, I edit everything manually :D
I think git-notes would show up below the fold but I haven’t done it before
See
[sendemail.cccmd]git setting, when you git-send-email it passes each patch file to this command and whatever it returns is added to the CC list.https://github.com/torvalds/linux/blob/master/scripts/get_maintainer.pl
https://www.kernel.org/doc/html/latest/process/submitting-patches.html#select-the-recipients-for-your-patch
I select recipients manually. get_maintainer is nice, and produces good suggestions, but it frequenty suggests too many people. For example, if you do a find/replace style commit which touches a lot of files, get_maintainer will suggest CCing you for a few years.
Yeah that’s true. I guess you can’t automate everything, you’d have to edit the get_maintainer.pl’s CC list before sending if you use it all the time.