All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Paulo Arcinas <pauloarcinas1982@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Qemu-devel Digest, Vol 112, Issue 523
Date: Mon, 23 Jul 2012 09:32:19 -0600	[thread overview]
Message-ID: <500D6E83.6050603@redhat.com> (raw)
In-Reply-To: <CAO1GuQWdkWwNDGyS6mc4UaWqzg1aavT6=sKQ-dnre6VNh3_miw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 970 bytes --]

On 07/23/2012 04:59 AM, Paulo Arcinas wrote:
> On Jul 23, 2012 6:47 PM, <qemu-devel-request@nongnu.org> wrote:
>>
>> Send Qemu-devel mailing list submissions to
>>         qemu-devel@nongnu.org
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>>         https://lists.nongnu.org/mailman/listinfo/qemu-devel
>> or, via email, send a message with subject or body 'help' to
>>         qemu-devel-request@nongnu.org
>>
>> You can reach the person managing the list at
>>         qemu-devel-owner@nongnu.org
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of Qemu-devel digest..."

Why are you even replying to a digest message in the first place,
wasting our bandwidth?  Please reply to specific messages, and trim the
portion of your reply that is not relevant to your followup.

-- 
Eric Blake   eblake@redhat.com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 620 bytes --]

      reply	other threads:[~2012-07-23 15:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.337968.1343040459.854.qemu-devel@nongnu.org>
2012-07-23 10:59 ` [Qemu-devel] Qemu-devel Digest, Vol 112, Issue 523 Paulo Arcinas
2012-07-23 15:32   ` Eric Blake [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=500D6E83.6050603@redhat.com \
    --to=eblake@redhat.com \
    --cc=pauloarcinas1982@gmail.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.