qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Willian Rampazzo <wrampazz@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	qemu-devel@nongnu.org
Cc: John Snow <jsnow@redhat.com>,
	Wainer dos Santos Moschetta <wainersm@redhat.com>,
	Matteo Croce <mcroce@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] MAINTAINERS: convert to JSON
Date: Thu, 13 May 2021 18:02:15 -0300	[thread overview]
Message-ID: <e49b9ef9-2d01-7a0d-38a1-2891c52a4279@redhat.com> (raw)
In-Reply-To: <c75b2eb6-4127-61e3-20e0-b572de89668d@redhat.com>

FYI, I had to setup Thunderbird to reply to you because Gmail web 
interface was crashing when I was trying to expand the e-mail to delete 
the code. So, as Peter mentioned, a nice April fools' joke.


On 5/13/21 3:32 PM, Philippe Mathieu-Daudé wrote:
> Cc'ing John/Willian/Wainer
> 

I think I understand why you brought this thread back now. Finding a way 
to correlate maintainers and tags is, indeed, a nice feature that can 
help with your idea about correlating tags and maintainers to use on tests.

The problem I see is that JSON is a good machine-readable file. It is a 
pain to edit it manually. So, despite the April fools' joke, my 
suggestion would be to create the JSON or any other machine-readable 
file from the MAINTAINERS file using a script.

> On 4/1/19 1:29 PM, Paolo Bonzini wrote:
>> JSON is already in wide use within QEMU for QMP and QAPI, enable
>> wider usage of MAINTAINERS by applying a well-defined machine-readable
>> format.
>>
>> Converting scripts/getmaintainers.pl is left for next year.

Year-base contribution!



  parent reply	other threads:[~2021-05-13 21:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-01 11:29 [Qemu-devel] [PATCH] MAINTAINERS: convert to JSON Paolo Bonzini
2021-05-13 18:32 ` Philippe Mathieu-Daudé
2021-05-13 18:54   ` John Snow
2021-05-13 18:54   ` Peter Maydell
2021-05-13 21:02   ` Willian Rampazzo [this message]
2021-05-14  5:31     ` Paolo Bonzini
2021-05-14 12:48       ` 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=e49b9ef9-2d01-7a0d-38a1-2891c52a4279@redhat.com \
    --to=wrampazz@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=mcroce@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --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).