On Mon, 2018-04-23 at 13:54 +0100, Daniel P. Berrangé wrote:
> 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>
> ---
> .gitpublish | 4 ++++
> 1 file changed, 4 insertions(+)
> create mode 100644 .gitpublish
>
> diff --git a/.gitpublish b/.gitpublish
> new file mode 100644
> index 0000000..16f6a01
> --- /dev/null
> +++ b/.gitpublish
> @@ -0,0 +1,4 @@
> +[gitpublishprofile "default"]
> +base = master
> +to = libvir-list@redhat.com
> +prefix = PATCH dbus
So far we send with prefix in opposite order, aka [libvirt][dbus PATCH]
but I see other libvirt subprojects use this format, so I guess we can
change it.
Katerina
--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list