All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PULL for-1.4 v2] Memory API ioport cleanups
Date: Tue, 15 Jan 2013 18:35:55 -0600	[thread overview]
Message-ID: <87libuarro.fsf@codemonkey.ws> (raw)
In-Reply-To: <50F5ED82.4070206@suse.de>

Andreas Färber <afaerber@suse.de> writes:

> Hi Anthony,
>
> Am 16.01.2013 00:02, schrieb Anthony Liguori:
>> 
>> Please adjust your pull request script to include a 0/M marker if you're
>> also including patches in the reply.
>
> In the past it was you who specifically requested us to always include
> the queue of patches part of that pull as reply! Is this no longer
> desired?

Yes, it is.  My patches tool handles PULL requests without them fine but
for QEMU, I want pull requests to include the patches being pulled.

If you're including patches (and you should), then the first mail should
indicate that it's the 0th mail of the series.

> Or how would I generate 0/M from my bash script? git-request-pull
> doesn't really fit into the "blurb" of a regular cover letter, coming
> with its own stats, so that I generate the mail headers by script.

I don't send pull requests so I'm the wrong person to ask.  Peter/Stefan, how
do ya'll do it?

Regards,

Anthony Liguori

>
> Regards,
> Andreas
>
>> No worries about this request, but my new version tracker gets confused
>> because it marks this whole series as "broken" because it's impossible
>> for a non-human to tell if this is the cover letter or something silly
>> like a new top-level patch posted to this thread.
>> 
>> Regards,
>> 
>> Anthony Liguori
>
> -- 
> SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
> GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

  reply	other threads:[~2013-01-16  0:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-15 18:47 [Qemu-devel] [PULL for-1.4 v2] Memory API ioport cleanups Andreas Färber
2013-01-15 18:47 ` [Qemu-devel] [PATCH 1/3] hw/dma.c: Fix conversion of ioport_register* to MemoryRegion Andreas Färber
2013-01-15 18:47 ` [Qemu-devel] [PATCH 2/3] xen_platform: Do not use old_portio-style callbacks Andreas Färber
2013-01-15 18:47   ` Andreas Färber
2013-01-15 18:47 ` [Qemu-devel] [PATCH 3/3] acpi_piix4: " Andreas Färber
2013-01-15 23:02 ` [Qemu-devel] [PULL for-1.4 v2] Memory API ioport cleanups Anthony Liguori
2013-01-16  0:00   ` Andreas Färber
2013-01-16  0:35     ` Anthony Liguori [this message]
2013-01-16 11:12       ` Peter Maydell
2013-01-16 12:56         ` Stefan Hajnoczi
2013-01-16  1:18 ` Anthony Liguori

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=87libuarro.fsf@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=afaerber@suse.de \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    /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.