From: Thomas Huth <thuth@redhat.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Stefan Hajnoczi" <stefanha@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-trivial@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] MAINTAINERS: Add trace-events and qemu-option-trace.texi to tracing section
Date: Wed, 9 May 2018 07:10:21 +0200 [thread overview]
Message-ID: <c91c4ff7-85d8-3605-7890-779abebea6fd@redhat.com> (raw)
In-Reply-To: <f0a24157-3aa9-4b51-8870-e83407e85697@amsat.org>
On 09.05.2018 07:02, Philippe Mathieu-Daudé wrote:
> Hi Thomas,
>
> On 05/09/2018 01:38 AM, Thomas Huth wrote:
>> The "trace-events" and "qemu-option-trace.texi" files in the top directory
>> are currently "unmaintained" according to scripts/get_maintainer.pl. They
>> obviously belong to the Tracing section, so add an entry for them there.
>
> I agree qemu-option-trace.texi belongs to the Tracing section,
> however I think trace-events is not specific to Tracing but belongs to
> everybody maintaining a C file in the top directory... Since they'll
> need to modify this file.
Right ... but what do you do if you just want to fix something in the
generic comments of that file? Who's then responsible for picking up the
patch? ... well, updates to comments could maybe go through
qemu-trivial, too, so I'm also fine if we do not list trace-events in
MAINTAINERS. I'll leave this up to Stefan to decide.
Thomas
next prev parent reply other threads:[~2018-05-09 5:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-09 4:38 [Qemu-devel] [PATCH] MAINTAINERS: Add trace-events and qemu-option-trace.texi to tracing section Thomas Huth
2018-05-09 5:02 ` Philippe Mathieu-Daudé
2018-05-09 5:10 ` Thomas Huth [this message]
2018-05-09 12:51 ` Eric Blake
2018-05-10 10:56 ` Stefan Hajnoczi
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=c91c4ff7-85d8-3605-7890-779abebea6fd@redhat.com \
--to=thuth@redhat.com \
--cc=f4bug@amsat.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=stefanha@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).