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..4b45752
--- /dev/null
+++ b/.gitpublish
@@ -0,0 +1,4 @@
+[gitpublishprofile "default"]
+base = master
+to = libvir-list@redhat.com
+prefix = PATCH cim
-- 
2.14.3

--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list

On Mon, Apr 23, 2018 at 01:54:20PM +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..4b45752
>--- /dev/null
>+++ b/.gitpublish
>@@ -0,0 +1,4 @@
>+[gitpublishprofile "default"]
>+base = master
>+to = libvir-list@redhat.com
>+prefix = PATCH cim

libvirt-cim has its own list:
https://www.redhat.com/mailman/listinfo/libvirt-cim

Jano

>-- 
>2.14.3
>
>--
>libvir-list mailing list
>libvir-list@redhat.com
>https://www.redhat.com/mailman/listinfo/libvir-list
--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list

On Mon, Apr 23, 2018 at 03:36:34PM +0200, Ján Tomko wrote:
> On Mon, Apr 23, 2018 at 01:54:20PM +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..4b45752
> > --- /dev/null
> > +++ b/.gitpublish
> > @@ -0,0 +1,4 @@
> > +[gitpublishprofile "default"]
> > +base = master
> > +to = libvir-list@redhat.com
> > +prefix = PATCH cim
> 
> libvirt-cim has its own list:
> https://www.redhat.com/mailman/listinfo/libvirt-cim

We stopped using that list though, largely because CIM itself is dead - so
if anyone does have a patch it should go to the main list.

We should in fact put an autoresponder on that list to kick any messages.

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|

--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list