This weekend I got down to solving a workflow problem that has been bugging me for some time: preparing and storing patch revisions. Manually managing patch revisions is painful; I often find myself switching between git and my inbox several times to put together a consistent patch series.
git-publish is a script that numbers patch revisions, optionally stores a cover letter, and submits the patches via git-send-email(1). When your tree is in a state that you wish to publish you say:
$ git publish --email@example.com
It creates a git tag that you can refer back to in the future and send out the patch series emails.
No more numbering revisions, copy & pasting cover letters, or running several steps to format and send patch series.
Give it a try if you are tired of manually managing patch revisions with git. git-publish is released under the MIT License at http://github.com/stefanha/git-publish. I have provided documentation but you can set it up in just two lines:
$ git clone git://github.com/stefanha/git-publish.git $ git-publish/git-publish --setup # make available via git alias
Be sure to check out the README - it explains how to install and run it in more detail.