Prepare and store patch revisions as git tags
https://github.com/stefanha/git-publish
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.
Version: 1.8.2
See also: git, git-absorb, git-annex, git-autofixup, git-cola, git-core-doc, git-cpan-patch, git-credential-azure, git-credential-oauth, git-crypt, git-cvs, git-daemon, git-email, git-extras, git-fame, git-filter-repo, git-ftp, git-gui, git-instaweb, git-lfs, git-merge-changelog, git-octopus, git-p4, git-remote-gcrypt, git-remote-hg, git-review, git-revise, git-secret, git-secrets, git-subtree, git-svn, git-tools, git-xcleaner.
General Commands | |
| git-publish | Prepare and store patch revisions as git tags |