From: Michael Tokarev <mjt@tls.msk.ru>
To: Chen Gang <gang.chen.5i5j@gmail.com>
Cc: qemu-trivial@nongnu.org, qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-trivial] Cc'ing emails [was: [PATCH] dump.c: Fix memory leak issue in cleanup processing for dump_init()]
Date: Mon, 04 Aug 2014 11:59:48 +0400 [thread overview]
Message-ID: <53DF3D74.9070503@msgid.tls.msk.ru> (raw)
In-Reply-To: <53DE5538.1020701@gmail.com>
Please stop Cc'ing me emails sent to, at least, qemu-trivial@.
I'm about to filter personal emails which are also sent to
some mailinglists I receive. I'd not do that, because this is
a good practice to Cc someone like that for various really
important or urgent emails, and if I to apply such a filter,
these urgent emails will be filtered too, obviously.
I'm not sure how people treat these cases or deal with them.
We are subscribed to, in particular, qemu-devel@, and active
maintainers look there too, so receive more than one copy of
many emails.
It is becoming worse. With get_maintainer.pl pulling addresses
of people who made changes or commits to files by default,
contributing to the project becomes a bit dangerous. Because
as a result, once you fix something, you're essentially being
subscribed to a spam list, because other contributors start
Ccing you for the patches with which you have absolutely nothing
to do, and if a discussion emerges, you can't opt out of it
anymore (especially for patches which raise hot discussions).
So I'd rather think twice before contributing anything...
Thanks,
/mjt
WARNING: multiple messages have this Message-ID (diff)
From: Michael Tokarev <mjt@tls.msk.ru>
To: Chen Gang <gang.chen.5i5j@gmail.com>
Cc: qemu-trivial@nongnu.org, qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Cc'ing emails [was: [PATCH] dump.c: Fix memory leak issue in cleanup processing for dump_init()]
Date: Mon, 04 Aug 2014 11:59:48 +0400 [thread overview]
Message-ID: <53DF3D74.9070503@msgid.tls.msk.ru> (raw)
In-Reply-To: <53DE5538.1020701@gmail.com>
Please stop Cc'ing me emails sent to, at least, qemu-trivial@.
I'm about to filter personal emails which are also sent to
some mailinglists I receive. I'd not do that, because this is
a good practice to Cc someone like that for various really
important or urgent emails, and if I to apply such a filter,
these urgent emails will be filtered too, obviously.
I'm not sure how people treat these cases or deal with them.
We are subscribed to, in particular, qemu-devel@, and active
maintainers look there too, so receive more than one copy of
many emails.
It is becoming worse. With get_maintainer.pl pulling addresses
of people who made changes or commits to files by default,
contributing to the project becomes a bit dangerous. Because
as a result, once you fix something, you're essentially being
subscribed to a spam list, because other contributors start
Ccing you for the patches with which you have absolutely nothing
to do, and if a discussion emerges, you can't opt out of it
anymore (especially for patches which raise hot discussions).
So I'd rather think twice before contributing anything...
Thanks,
/mjt
next prev parent reply other threads:[~2014-08-04 8:00 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-03 15:28 [Qemu-trivial] [PATCH] dump.c: Fix memory leak issue in cleanup processing for dump_init() Chen Gang
2014-08-03 15:28 ` [Qemu-devel] " Chen Gang
2014-08-03 15:56 ` [Qemu-trivial] " Laszlo Ersek
2014-08-03 15:56 ` [Qemu-devel] " Laszlo Ersek
2014-08-04 13:51 ` [Qemu-trivial] " Chen Gang
2014-08-04 13:51 ` [Qemu-devel] " Chen Gang
2014-08-11 19:47 ` [Qemu-trivial] " Chen Gang
2014-08-11 19:47 ` [Qemu-devel] " Chen Gang
2014-08-04 7:59 ` Michael Tokarev [this message]
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 ` [Qemu-trivial] " Chen Gang
2014-08-04 14:13 ` [Qemu-devel] " Chen Gang
2014-08-04 15:43 ` [Qemu-trivial] [Qemu-devel] Cc'ing emails [ Markus Armbruster
2014-08-04 15:43 ` Markus Armbruster
2014-08-05 4:41 ` [Qemu-trivial] " Chen Gang
2014-08-05 4:41 ` Chen Gang
2014-08-05 7:08 ` [Qemu-trivial] " Michael Tokarev
2014-08-05 7:08 ` Michael Tokarev
2014-08-05 8:07 ` [Qemu-trivial] " Peter Maydell
2014-08-05 8:07 ` Peter Maydell
2014-08-05 12:20 ` [Qemu-trivial] " Chen Gang
2014-08-05 12:20 ` Chen Gang
2014-08-05 9:41 ` [Qemu-trivial] " Markus Armbruster
2014-08-05 9:41 ` Markus Armbruster
2014-08-05 13:25 ` [Qemu-trivial] " Anthony Liguori
2014-08-05 13:25 ` Anthony Liguori
2014-08-12 15:43 ` [Qemu-trivial] [PATCH] dump.c: Fix memory leak issue in cleanup processing for dump_init() Laszlo Ersek
2014-08-12 15:43 ` [Qemu-devel] " Laszlo Ersek
2014-08-12 22:19 ` [Qemu-trivial] " Chen Gang
2014-08-12 22:19 ` [Qemu-devel] " Chen Gang
2014-08-14 20:49 ` [Qemu-trivial] " Luiz Capitulino
2014-08-14 20:49 ` [Qemu-devel] " Luiz Capitulino
2014-08-14 22:03 ` [Qemu-trivial] " Chen Gang
2014-08-14 22:03 ` [Qemu-devel] " 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=53DF3D74.9070503@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=gang.chen.5i5j@gmail.com \
--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 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.