qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Wainer dos Santos Moschetta <wainersm@redhat.com>,
	Willian Rampazzo <wrampazz@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH v2] MAINTAINERS: Merge the Gitlab-CI section into the generic CI section
Date: Mon, 8 Mar 2021 18:01:41 +0100	[thread overview]
Message-ID: <8532b756-f53c-e606-b900-6dc77527fd71@redhat.com> (raw)
In-Reply-To: <78fb219e-fba5-0dfc-b21e-0cc657a9c372@amsat.org>

On 08/03/2021 17.35, Philippe Mathieu-Daudé wrote:
> On 3/8/21 4:46 PM, Thomas Huth wrote:
>> 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.
>>
>> 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.
>>
>> Now to avoid that Alex is listed here alone, Philippe and I agreed to
>> help as backup maintainers here, too.
>>
>> Signed-off-by: Thomas Huth <thuth@redhat.com>
>> ---
>>   v2: Keep Philippe and myself as maintainer instead of reviewer
>>
>>   MAINTAINERS | 21 +++++++--------------
>>   1 file changed, 7 insertions(+), 14 deletions(-)
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index 26c9454823..5c4c179abb 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -3262,17 +3262,21 @@ F: include/hw/remote/iohub.h
>>   
>>   Build and test automation
>>   -------------------------
>> -Build and test automation
>> +Build and test automation, Linux Continuous Integration
> 
> I'd rather not limit it to Linux hosts...
> 
>>   M: Alex Bennée <alex.bennee@linaro.org>
>> -M: Fam Zheng <fam@euphon.net>
> 
> I'm not sure about Fam removal, he is the one maintaining patchew
> (see [*] below)... Maybe we need an Ack from Paolo?

We could split the Patchew part into a separate section... OTOH, there are 
no patchew related files in the main git repo anyway that we track in the 
MAINTAINERS file, so maybe it makes more sense to simply remove that line? 
(Patchew admins are already mentioned here: 
https://wiki.qemu.org/AdminContacts )

  Thomas



  reply	other threads:[~2021-03-08 17:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-08 15:46 [PATCH v2] MAINTAINERS: Merge the Gitlab-CI section into the generic CI section Thomas Huth
2021-03-08 16:35 ` Philippe Mathieu-Daudé
2021-03-08 17:01   ` Thomas Huth [this message]
2021-03-08 17:52     ` Philippe Mathieu-Daudé
2021-03-08 17:29 ` Wainer dos Santos Moschetta
2021-03-08 17:49 ` Willian Rampazzo
2021-03-08 19:12   ` Philippe Mathieu-Daudé
2021-03-09 12:45 ` Alex Bennée
2021-03-10 17:01 ` Fam Zheng

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=8532b756-f53c-e606-b900-6dc77527fd71@redhat.com \
    --to=thuth@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=f4bug@amsat.org \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --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 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).