Prepare and store patch revisions as git tags
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.
Release | Stable | Testing |
---|---|---|
Fedora Rawhide | 1.7.0-2.fc35 | - |
Fedora 35 | 1.7.0-2.fc35 | - |
Fedora 34 | 1.7.0-1.fc34 | - |
EPEL 8 | 1.6.1-1.el8 | - |
EPEL 7 | 1.6.1-1.el7 | - |
You can contact the maintainers of this package via email at
git-publish dash maintainers at fedoraproject dot org
.