Skip to content

stefanha/git-publish

master
Switch branches/tags
Code

Latest commit

Normally email messages have subject headers, but if the user edits the
email in their editor and makes it empty (probably because they changed
their mind and don't want to send an email yet) then git-publish
crashes:

  Traceback (most recent call last):
    File "git-publish/git-publish", line 953, in <module>
      sys.exit(main())
    File "git-publish/git-publish", line 910, in main
      selected_patches = inspect_menu(tmpdir, to, cc, patches, suppress_cc,
    File "git-publish/git-publish", line 507, in inspect_menu
      print(m['Subject'].strip())
  AttributeError: 'NoneType' object has no attribute 'strip'

Skip printing the Subject header when it doesn't exist.

Signed-off-by: Stefan Hajnoczi <stefanha@gmail.com>
6fdef78

Git stats

Files

Permalink
Failed to load latest commit information.

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.

How to install

Packages

Packages are available for:

Manual install

You 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/

git publish alias

Run git-publish --setup to install the git alias so you can invoke git publish instead of git-publish.

How it works

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

Documentation

Read the man page here.

Get in touch

Please submit pull requests on GitHub (https://github.com/stefanha/git-publish) or email patches to Stefan Hajnoczi stefanha@gmail.com.

About

Prepare and store patch revisions as git tags

Resources

License

Stars

Watchers

Forks

Packages

No packages published