Tired of manually creating patch series emails?
git-publish prepares patches and stores them as git tags for future reference. It works with individual patches as well as patch series. Revision numbering is handled automatically.
No constraints are placed on git workflow, both vanilla git commands and custom workflow scripts are compatible with git-publish.
Email sending and pull requests are fully integrated so that publishing patches can be done in a single command.
Hook scripts are invoked during patch preparation so that custom checks or test runs can be automated.
Packages are available for:
dnf install git-publishapt install git-publishyum install git-publishYou can also run git-publish from the source tree (useful for development). Assuming ~/bin is on $PATH:
$ git clone https://github.com/stefanha/git-publish
$ ln -s $PWD/git-publish/git-publish ~/bin/
Run git-publish --setup to install the git alias so you can invoke git publish instead of git-publish.
Send the initial patch series email like this:
$ git publish --to patches@example.org --cc maintainer@example.org
You will be prompted for a cover letter on a multi-patch series and you will be presented with a chance to review the emails before they are sent.
Sending successive revisions is easy, you don't need to repeat all the details since git-publish stores them for you:
$ git publish # to send v2, v3, etc
Read the man page here.
Please submit pull requests on GitHub (https://github.com/stefanha/git-publish) or email patches to Stefan Hajnoczi stefanha@gmail.com.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4