qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Glauber Costa <glommer@redhat.com>,
	qemu-devel@nongnu.org, armbru@redhat.com
Subject: Re: [Qemu-devel] sending pci information over the wire
Date: Fri, 19 Jun 2009 10:16:01 -0500	[thread overview]
Message-ID: <4A3BABB1.6060708@codemonkey.ws> (raw)
In-Reply-To: <4A3BA1C6.6040701@redhat.com>

Gerd Hoffmann wrote:
>> I think something
>> we could do better is avoiding losing track of patches though. I'm
>> working on that.
>
> Related issues:  Looks like the qemu-commits list is lossy.  I havn't 
> seen messages for my two most recent vnc patches.  I figured while 
> rebasing the vnc patches because git surprised me with "nothing to 
> do".  Also it seems for merges only a message for the merge commit 
> goes to the list, not for the individual patches.

With respect to merge commits, it wouldn't surprise me.

There is a certain amount of lossy-ness to qemu-commits because our 
internal SMTP servers frequently like to go down.  It's a git commit 
hook so having a mechanism to retry later would be overly complicated.

Regards,

Anthony Liguori

> cheers,
>   Gerd

  parent reply	other threads:[~2009-06-19 15:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-18 19:39 [Qemu-devel] sending pci information over the wire Glauber Costa
2009-06-18 20:03 ` Anthony Liguori
2009-06-18 20:12   ` Glauber Costa
2009-06-18 20:38     ` Anthony Liguori
2009-06-19  8:55       ` Gerd Hoffmann
2009-06-19 13:10         ` Anthony Liguori
2009-06-19 14:33           ` Gerd Hoffmann
2009-06-19 14:47             ` Paul Brook
2009-06-19 15:16             ` Anthony Liguori [this message]
2009-06-19 15:38               ` Gerd Hoffmann
2009-06-19 15:56                 ` Anthony Liguori
2009-06-20 18:58   ` 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=4A3BABB1.6060708@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=armbru@redhat.com \
    --cc=glommer@redhat.com \
    --cc=kraxel@redhat.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).