qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jamie Lokier <jamie@shareable.org>
To: "François Revol" <revol@free.fr>
Cc: Jan Kiszka <jan.kiszka@siemens.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: qemu-devel now defaults to reply-to "poster"
Date: Tue, 21 Apr 2009 12:12:41 +0100	[thread overview]
Message-ID: <20090421111241.GB893@shareable.org> (raw)
In-Reply-To: <6281256924-BeMail@laptop>

François Revol wrote:
> I thought the purpose of a mailing list was to handle the *list* of
> people to **mail* to automatically... looks like offloading to humans
> back...

Nice idea.

But it only works for low traffic lists and people who are not busy.

Your idea of a mailing list doesn't work for people who don't have
time to read the whole list, but who it's important to involve in
specific threads.

For example, someone reporting a bug should see the replies to their
specific report, but often they won't have time to check the whole
list every day for replies.  Same for things which touch subsystems
with specific maintainers.

Cc lets you make sure specific people are involved in specific
threads.  Nobody's created a mailing-list header
"X-This-Message-Is-Important-To-The-Following-People:" which you'd
need otherwise.

Cc does that job, and if you have a good mail setup then you don't see
the message twice, it just flags it as important to the named people.

Which is why most development lists use group-reply and Cc, and many
where it's not important (such as chat lists) use list-reply.

-- Jamie

  parent reply	other threads:[~2009-04-21 11:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-20 21:50 [Qemu-devel] qemu-devel now defaults to reply-to "poster" Anthony Liguori
2009-04-20 22:19 ` François Revol
2009-04-21  5:50 ` Avi Kivity
2009-04-21  9:29 ` [Qemu-devel] " Jan Kiszka
2009-04-21 10:42   ` François Revol
2009-04-21 11:11     ` Jan Kiszka
2009-04-21 11:12     ` Jamie Lokier [this message]
2009-04-21 12:32     ` Avi Kivity

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=20090421111241.GB893@shareable.org \
    --to=jamie@shareable.org \
    --cc=jan.kiszka@siemens.com \
    --cc=qemu-devel@nongnu.org \
    --cc=revol@free.fr \
    /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).