From: "Michael S. Tsirkin" <mst@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Carsten Otte <cotte@de.ibm.com>,
markmc@redhat.com, qemu-devel@nongnu.org,
Christian Borntraeger <borntraeger@de.ibm.com>,
kraxel@redhat.com, Avi Kivity <avi@redhat.com>,
Paul Brook <paul@codesourcery.com>
Subject: [Qemu-devel] Re: qemu: tree for pci related fixes
Date: Wed, 23 Sep 2009 22:38:58 +0300 [thread overview]
Message-ID: <20090923193858.GD18947@redhat.com> (raw)
In-Reply-To: <4ABA64E4.7070007@codemonkey.ws>
On Wed, Sep 23, 2009 at 01:11:48PM -0500, Anthony Liguori wrote:
> I think it makes sense for everyone to keep their own trees and to make
> them publicly accessible. However, for resends, I would still like them
> to occur on the mailing list.
Okay I guess .. but why?
next prev parent reply other threads:[~2009-09-23 19:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-23 15:56 [Qemu-devel] qemu: tree for pci related fixes Michael S. Tsirkin
2009-09-23 18:11 ` [Qemu-devel] " Anthony Liguori
2009-09-23 19:38 ` Michael S. Tsirkin [this message]
2009-09-23 20:38 ` Anthony Liguori
2009-09-24 4:18 ` Michael S. Tsirkin
2009-09-24 6:38 ` Avi Kivity
2009-09-24 4:41 ` Michael S. Tsirkin
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=20090923193858.GD18947@redhat.com \
--to=mst@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=cotte@de.ibm.com \
--cc=kraxel@redhat.com \
--cc=markmc@redhat.com \
--cc=paul@codesourcery.com \
--cc=qemu-devel@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).