From: Chen Gang <gang.chen.5i5j@gmail.com>
To: Peter Maydell <peter.maydell@linaro.org>,
Michael Tokarev <mjt@tls.msk.ru>
Cc: QEMU Trivial <qemu-trivial@nongnu.org>,
Markus Armbruster <armbru@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Cc'ing emails [
Date: Tue, 05 Aug 2014 20:20:40 +0800 [thread overview]
Message-ID: <53E0CC18.7070403@gmail.com> (raw)
In-Reply-To: <CAFEAcA_9+5VEzf4dpyrs9tR-jici+ea6rr6qh6F+nX296PH8hQ@mail.gmail.com>
On 08/05/2014 04:07 PM, Peter Maydell wrote:
> n 5 August 2014 08:08, Michael Tokarev <mjt@tls.msk.ru> wrote:
>> 05.08.2014 08:41, Chen Gang wrote:
>>>
>>> Every members have their own tastes, and one working flow may be not
>>> suitable for all members. I can understand, and hope other members
>>> understand too.
>>>
>>> At least for me, next, I shall send patch to the members which I can get
>>> from 'get_maintainers.pl' and only Cc to qemu-devel. And shall skip
>>> qemu-trivial and Michael Tokarev.
>>
>> Why skip both? It's your call, but I'm curious.
>
> I think that is a misunderstanding. You asked not to get mails
> cc'd to both you personally and qemu-trivial at the same time,
> and Chen misread this to mean not to cc either address.
>
> Trivial patches should still be sent "To: qemu-devel + Cc: qemu-trivial".
>
OK, thank you for your explanation. Excuse me, my English is not quite
well, originally, I really misunderstood what Michael Tokarev said.
>> What I _think_ wrong is that get_maintainers.pl lists many random
>> "patchers" for a given file by default.
>
> Yes, I think it's probably reasonable to change it to make it not
> default to "--git-fallback". Do you want to submit a patch?
>
> (Perhaps we could make it cc qemu-orphan@ if we wanted to
> flag up holes in our MAINTAINERS coverage and patches liable
> to get lost, but that probably only makes sense if we have people
> who would care enough to do that monitoring work.)
>
Originally, I assumed Michael Tokarev is that role (be the people who
would care enough to do that monitoring work), but sorry, at present,
I know, I misunderstand him (he is not this role).
It is really hard to find a member to act as this role (I guess, for act
as this role, he/she will be a real global maintainer of qemu).
Thanks.
--
Chen Gang
Open, share, and attitude like air, water, and life which God blessed
next prev parent reply other threads:[~2014-08-05 12:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-03 15:28 [Qemu-devel] [PATCH] dump.c: Fix memory leak issue in cleanup processing for dump_init() Chen Gang
2014-08-03 15:56 ` Laszlo Ersek
2014-08-04 13:51 ` Chen Gang
2014-08-11 19:47 ` Chen Gang
2014-08-04 7:59 ` [Qemu-devel] Cc'ing emails [was: [PATCH] dump.c: Fix memory leak issue in cleanup processing for dump_init()] Michael Tokarev
2014-08-04 14:13 ` Chen Gang
2014-08-04 15:43 ` [Qemu-devel] Cc'ing emails [ Markus Armbruster
2014-08-05 4:41 ` Chen Gang
2014-08-05 7:08 ` Michael Tokarev
2014-08-05 8:07 ` Peter Maydell
2014-08-05 12:20 ` Chen Gang [this message]
2014-08-05 9:41 ` Markus Armbruster
2014-08-05 13:25 ` Anthony Liguori
2014-08-12 15:43 ` [Qemu-devel] [PATCH] dump.c: Fix memory leak issue in cleanup processing for dump_init() Laszlo Ersek
2014-08-12 22:19 ` Chen Gang
2014-08-14 20:49 ` Luiz Capitulino
2014-08-14 22:03 ` Chen Gang
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=53E0CC18.7070403@gmail.com \
--to=gang.chen.5i5j@gmail.com \
--cc=armbru@redhat.com \
--cc=mjt@tls.msk.ru \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
/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).