From: Stefan Hajnoczi <stefanha@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Thomas Huth" <thuth@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Mark Cave-Ayland" <mark.cave-ayland@ilande.co.uk>,
qemu-devel <qemu-devel@nongnu.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Edgar E. Iglesias" <edgar.iglesias@gmail.com>
Subject: Re: [RFC] Using gitlab for upstream qemu repo?
Date: Fri, 23 Oct 2020 14:41:13 +0100 [thread overview]
Message-ID: <20201023134113.GA812157@stefanha-x1.localdomain> (raw)
In-Reply-To: <20201023085131.GC445638@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 674 bytes --]
On Fri, Oct 23, 2020 at 09:51:31AM +0100, Daniel P. Berrangé wrote:
> Not commonly known is that GitLab also has support for Git push options,
> which let you create merge requests using a plain "git push":
>
> https://docs.gitlab.com/ee/user/project/push_options.html
>
> eg if you have a remote called "gitlab", you can open a MR from the CLI
> using
>
> $ git push -o merge_request.create \
> -o merge_request.title="Do awesome thing" \
> gitlab my-branch
>
> This is something that I could see being easily wired up into a
> "git-publish" like tool for example.
Nice, thanks for mentioning this GitLab feature.
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-10-23 13:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-22 16:47 [RFC] Using gitlab for upstream qemu repo? Paolo Bonzini
2020-10-22 17:24 ` Eric Blake
2020-10-23 7:37 ` Gerd Hoffmann
2020-10-23 8:51 ` Daniel P. Berrangé
2020-10-23 13:41 ` Stefan Hajnoczi [this message]
2020-10-23 9:37 ` Paolo Bonzini
2020-10-23 8:44 ` Daniel P. Berrangé
2020-10-23 13:41 ` Stefan Hajnoczi
2020-10-26 11:04 ` Peter Maydell
2020-10-27 13:14 ` Michael Roth
2020-10-27 18:48 ` Paolo Bonzini
2020-10-27 14:08 ` Stefan Hajnoczi
2020-10-27 14:20 ` Daniel P. Berrangé
2020-10-27 14:32 ` Peter Maydell
2021-01-05 14:12 ` Peter Maydell
2021-01-11 9:57 ` Stefan Hajnoczi
2021-01-11 11:02 ` Paolo Bonzini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201023134113.GA812157@stefanha-x1.localdomain \
--to=stefanha@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=edgar.iglesias@gmail.com \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.