diff options
| author | Daniel P. Berrangé <berrange@redhat.com> | 2018-04-23 13:46:47 +0100 |
|---|---|---|
| committer | Daniel P. Berrangé <berrange@redhat.com> | 2018-04-24 10:46:59 +0100 |
| commit | 41e0a95f509cfc4e6ab6e842965ba67008f26658 (patch) | |
| tree | 522a3109151503ded7d2e77a275ebbc1d94d6bba | |
| parent | c99ed22847eaa028cf09960b01213f92b8121d3d (diff) | |
| download | libvirt-python-41e0a95f509cfc4e6ab6e842965ba67008f26658.tar.gz | |
git: add config file telling git-publish how to send patchesv4.3.0
The "git-publish" tool is a useful git extension for sending patch
series for code review. It automatically creates versioned tags
each time code on a branch is sent, so that there is a record of
each version. It also remembers the cover letter so it does not
need re-entering each time the series is reposted.
With this config file present it is now sufficient[1] to run
$ git publish
to send all patches in a branch to the list for review, with the
correct subject prefix added for this non-core libvirt module.
[1] Assuming your $HOME/.gitconfig has an SMTP server listed
at least e.g.
[sendemail]
smtpserver = smtp.example.com
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
| -rw-r--r-- | .gitpublish | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/.gitpublish b/.gitpublish new file mode 100644 index 0000000..2fe1539 --- /dev/null +++ b/.gitpublish @@ -0,0 +1,4 @@ +[gitpublishprofile "default"] +base = master +to = libvir-list@redhat.com +prefix = python PATCH |