From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>, qemu-devel@nongnu.org
Cc: "Thomas Huth" <thuth@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>
Subject: Re: [PATCH 3/3] gitlab: assign python helper files to GitLab maintainers section
Date: Fri, 18 Sep 2020 15:47:57 +0200 [thread overview]
Message-ID: <70042db8-bed1-523e-a0a9-565bf6d5c74d@redhat.com> (raw)
In-Reply-To: <20200918132903.1848939-4-berrange@redhat.com>
On 9/18/20 3:29 PM, Daniel P. Berrangé wrote:
> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
> ---
> MAINTAINERS | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 3d17cad19a..b60981fb62 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -3097,6 +3097,7 @@ R: Wainer dos Santos Moschetta <wainersm@redhat.com>
> S: Maintained
> F: .gitlab-ci.yml
> F: .gitlab-ci.d/crossbuilds.yml
> +F: .gitlab-ci.d/*py
Squash in 1st patch?
Regardless:
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
next prev parent reply other threads:[~2020-09-18 13:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-18 13:29 [PATCH 0/3] gitlab: add jobs for checking paches Daniel P. Berrangé
2020-09-18 13:29 ` [PATCH 1/3] gitlab: add a CI job for running checkpatch.pl Daniel P. Berrangé
2020-09-18 13:46 ` Philippe Mathieu-Daudé
2020-10-13 8:08 ` Thomas Huth
2020-10-13 8:09 ` Daniel P. Berrangé
2020-09-18 13:29 ` [PATCH 2/3] gitlab: add a CI job to validate the DCO sign off Daniel P. Berrangé
2020-09-18 13:29 ` [PATCH 3/3] gitlab: assign python helper files to GitLab maintainers section Daniel P. Berrangé
2020-09-18 13:47 ` Philippe Mathieu-Daudé [this message]
2020-09-18 13:36 ` [PATCH 0/3] gitlab: add jobs for checking paches no-reply
2020-09-18 13:54 ` no-reply
2020-09-18 14:07 ` Thomas Huth
2020-09-18 14:10 ` Philippe Mathieu-Daudé
2020-09-18 14:15 ` Daniel P. Berrangé
2020-09-18 14:19 ` 罗勇刚(Yonggang Luo)
2020-09-18 14:57 ` no-reply
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=70042db8-bed1-523e-a0a9-565bf6d5c74d@redhat.com \
--to=philmd@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=wainersm@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).