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: Thu, 24 Sep 2009 07:18:56 +0300 [thread overview]
Message-ID: <20090924041856.GA21782@redhat.com> (raw)
In-Reply-To: <4ABA874D.9040801@codemonkey.ws>
On Wed, Sep 23, 2009 at 03:38:37PM -0500, Anthony Liguori wrote:
> Michael S. Tsirkin wrote:
>> 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?
>>
> Resends happen for one of two reasons. Either I'm too slow and the
> sender is impatient or I've dropped the patch and not provided
> appropriate explanation. I see both cases as a failure on my part and
> [RESEND] on the list gets my attention much better than having a git
> tree.
>
> Regards,
>
> Anthony Liguori
OK, so the tree will complement RESENDs, not replace them.
Maybe I'll try to script something that converts old patches to RESENDs,
we'll see.
--
MST
next prev parent reply other threads:[~2009-09-24 4:21 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
2009-09-23 20:38 ` Anthony Liguori
2009-09-24 4:18 ` Michael S. Tsirkin [this message]
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=20090924041856.GA21782@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 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.