All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Thomas Huth <thuth@redhat.com>
Cc: "Fam Zheng" <fam@euphon.net>,
	"Willian Rampazzo" <wrampazz@redhat.com>,
	qemu-devel@nongnu.org,
	"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
	"Philippe Mathieu-Daudé" <f4bug@amsat.org>
Subject: Re: [PATCH v3] MAINTAINERS: Merge the Gitlab-CI section into the generic CI section
Date: Tue, 09 Mar 2021 16:25:41 +0000	[thread overview]
Message-ID: <87tupk8far.fsf@linaro.org> (raw)
In-Reply-To: <20210309112356.737266-1-thuth@redhat.com>


Thomas Huth <thuth@redhat.com> writes:

> The status of the gitlab-CI files is currently somewhat confusing, and
> it is often not quite clear whether a patch should go via my tree or
> via the testing tree of Alex. That situation has grown historically...
> Initially, I was the only one using the gitlab-CI, just for my private
> repository there. But in the course of time, the gitlab-CI switched to
> use the containers from tests/docker/ (which is not part of the gitlab-CI
> section in the MAINTAINERS file), and QEMU now even switched to gitlab.com
> completely for the repository and will soon use it as its gating CI, too,
> so it makes way more sense if the gitlab-ci.yml files belong to the people
> who are owning the qemu-project on gitlab.com and take care of the gitlab
> CI there. Thus let's merge the gitlab-ci section into the common "test and
> build automation" section.
>
> And while we're at it, I'm also removing the line with Fam there for now,
> since he was hardly active during the last years in this area anymore.
> If he ever gets more time for this part again in the future, we surely
> can add the line back again. I'm also removing the Patchew URL from this
> section now since Patchew's files are not tracked in the main QEMU repo
> and it is also not maintained by Alex, Philippe and myself.
> The maintainers of Patchew are still listed more accurately in the wiki on
> https://wiki.qemu.org/AdminContacts & https://wiki.qemu.org/Testing/CI/Patchew
> instead.
>
> Now to avoid that Alex is listed here in this section alone, Philippe and
> I agreed to help as backup maintainers here, too. And Willian volunteered
> to be an additional reviewer.
>
> Acked-by: Wainer dos Santos Moschetta <wainersm@redhat.com>
> Acked-by: Willian Rampazzo <willianr@redhat.com>
> Signed-off-by: Thomas Huth <thuth@redhat.com>

Reviewed-by: Alex Bennée <alex.bennee@linaro.org>

-- 
Alex Bennée


  parent reply	other threads:[~2021-03-09 18:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-09 11:23 [PATCH v3] MAINTAINERS: Merge the Gitlab-CI section into the generic CI section Thomas Huth
2021-03-09 11:51 ` Philippe Mathieu-Daudé
2021-03-09 16:25 ` Alex Bennée [this message]
2021-03-10 13:04 ` Willian Rampazzo

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=87tupk8far.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=f4bug@amsat.org \
    --cc=fam@euphon.net \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.com \
    --cc=wainersm@redhat.com \
    --cc=wrampazz@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.