From: Avi Kivity <avi@qumranet.com>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Linux Kernel mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] Time for a linux-kvm mailing list?
Date: Mon, 19 Feb 2007 10:19:30 +0200 [thread overview]
Message-ID: <45D95D92.4010507@qumranet.com> (raw)
In-Reply-To: <45D8B786.7010609@tmr.com>
Bill Davidsen wrote:
> Why would I post it to a list where it's off-topic by list name? And
> how would anyone know that the list name can be ignored when so many
> other lists with "devel" in the name tell people with user questions
> to go elsewhere? Right now only users who ignore list names would even
> look there.
>
I added some text to the list description[1] to make it clear that user
queries are not off-topic.
[1] http://kvm.qumranet.com/kvmwiki/Lists,_IRC
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
prev parent reply other threads:[~2007-02-19 8:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-17 20:40 [RFC] Time for a linux-kvm mailing list? Bill Davidsen
2007-02-18 9:16 ` Avi Kivity
2007-02-18 20:31 ` Bill Davidsen
2007-02-19 8:19 ` Avi Kivity [this message]
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=45D95D92.4010507@qumranet.com \
--to=avi@qumranet.com \
--cc=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.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