On Thu, Sep 17, 2020 at 5:36 PM Daniel P. Berrangé
wrote:
>
> On Thu, Sep 17, 2020 at 10:53:14AM +0200, Paolo Bonzini wrote:
> > On 17/09/20 10:16, Philippe Mathieu-Daudé wrote:
> > > patchew is currently pushing successfully applied series
> > > (using the cover Message-ID as tag) to GitHub.
> >
Hi,
> What if we used git-publish to always push to gitlab when submitting
> patches, and have it include the gitlab ref in the cover letter.
Well, when pushing to gitlab anyway for CI runs this should be done
*before* publishing the patch series on the list ...
> That would trigger CI jobs in
On Thu, Sep 17, 2020 at 10:53:14AM +0200, Paolo Bonzini wrote:
> On 17/09/20 10:16, Philippe Mathieu-Daudé wrote:
> > patchew is currently pushing successfully applied series
> > (using the cover Message-ID as tag) to GitHub.
> > This is very handy (no need to apply patches manually):
> > https://g
On 17/09/20 10:16, Philippe Mathieu-Daudé wrote:
> patchew is currently pushing successfully applied series
> (using the cover Message-ID as tag) to GitHub.
> This is very handy (no need to apply patches manually):
> https://github.com/patchew-project/qemu/tags
>
> Can we push the same that to an
Hi,
patchew is currently pushing successfully applied series
(using the cover Message-ID as tag) to GitHub.
This is very handy (no need to apply patches manually):
https://github.com/patchew-project/qemu/tags
Can we push the same that to an equivalent GitLab account?
We could then have a script r