public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Jes Sorensen <jes@sgi.com>
To: Avi Kivity <avi@qumranet.com>
Cc: kvm-ppc-devel@lists.sourceforge.net,
	kvm-devel <kvm-devel@lists.sourceforge.net>,
	kvm-ia64-devel@lists.sourceforge.net,
	Hollis Blanchard <hollisb@us.ibm.com>,
	postmaster@vger.kernel.org
Subject: Re: [kvm-ppc-devel] Moving kvm lists to kernel.org?
Date: 25 Apr 2008 05:18:30 -0400	[thread overview]
Message-ID: <yq0fxtajnrt.fsf@jaguar.mkp.net> (raw)
In-Reply-To: <4810ACD3.3030507@qumranet.com>

>>>>> "Avi" == Avi Kivity <avi@qumranet.com> writes:

Avi> kvm-devel doesn't do manual moderation.  If vger has the
Avi> infrastructure, I don't see why you can't continue doing this on
Avi> kvm-ppc-devel.

Please don't do this for the kvm-ia64 list either.

Avi> btw, we can probably shorten the names to kvm@ and kvm-$arch@
Avi> while we're at it.

Either way works IMHO.

Cheers,
Jes

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone

  reply	other threads:[~2008-04-25  9:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-24 12:54 Moving kvm lists to kernel.org? Avi Kivity
2008-04-24 13:03 ` Yang, Sheng
2008-04-24 13:26 ` David Miller
2008-04-24 13:33   ` Avi Kivity
2008-04-24 19:43   ` Andi Kleen
2008-04-24 15:46 ` [kvm-ppc-devel] " Hollis Blanchard
2008-04-24 15:52   ` Avi Kivity
2008-04-25  9:18     ` Jes Sorensen [this message]
2008-04-27  9:40 ` Avi Kivity
2008-04-29 10:30   ` David Miller
2008-04-29 21:46     ` Avi Kivity
2008-04-30  3:14       ` David Miller
2008-04-30  9:18         ` 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=yq0fxtajnrt.fsf@jaguar.mkp.net \
    --to=jes@sgi.com \
    --cc=avi@qumranet.com \
    --cc=hollisb@us.ibm.com \
    --cc=kvm-devel@lists.sourceforge.net \
    --cc=kvm-ia64-devel@lists.sourceforge.net \
    --cc=kvm-ppc-devel@lists.sourceforge.net \
    --cc=postmaster@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