git-publish handles repetitive and time-consuming details of managing patch
email submission. It works with individual patches as well as patch series and
has support for pull request emails.
Each revision is stored as a git tag including the cover letter (if any). This
makes it easy to refer back to previous revisions of a patch. Numbering is
handled automatically and the To:/Cc: email addresses are remembered across
revisions to save you retyping them.
Many projects have conventions for submitting patches. It is possible to
encode them as a .gitpublish file and hooks/ scripts. This automatically uses
the right settings and can run a coding style checker or linting tools before
emails are sent. |