qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Ken Moffat <zarniwhoop@ntlworld.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	Anthony Liguori <aliguori@amazon.com>,
	"patches@linaro.org" <patches@linaro.org>
Subject: Re: [Qemu-devel] [PATCH for-1.7] configure: Explicitly set ARFLAGS so we can build with GNU Make 4.0
Date: Tue, 05 Nov 2013 20:31:16 +0100	[thread overview]
Message-ID: <52794784.2020304@suse.de> (raw)
In-Reply-To: <CAFEAcA-v09Bg_JBrRApstuAU=yTRFnn04695Z-y78R9SNDktNw@mail.gmail.com>

Am 05.11.2013 20:09, schrieb Peter Maydell:
> On 5 November 2013 18:45, Andreas Färber <afaerber@suse.de> wrote:
>> Am 05.11.2013 19:04, schrieb Peter Maydell:
>>> Ping!
>>
>> A typo in the commit message has been reported
> 
> What typo? Alex sent a reply claiming that there was
> a missing space in the subject but that appears to be
> entirely his email client's problem, since as you can
> see from this mail and also in Linaro's patchwork
> http://patches.linaro.org/21203/ there is a space there.
> (I would link to the qemu patchwork but it seems to
> be down right now.)

Looks like you're right. You replying to his claim would've helped. ;)

>> , and it has been
>> requested to add Cc: qemu-stable@nongnu.org.
> 
> I don't think there's any need to respin a patch
> just because somebody thinks it might be worth
> applying to stable.

Point is, if you are ping'ing Anthony to apply this with his
fully-automated patches tool, then he won't add the Cc and in turn it
will unlikely be backported to 1.6.2.

The response I got at QEMU Summit was that it is both the contributor's
and the submaintainer's responsibility to add the Cc to the commit
message. But maybe you're going to tell me that I misunderstood that as
well...

Andreas

-- 
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-11-05 19:31 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-05 19:09 [Qemu-devel] [PATCH for-1.7] configure: Explicitly set ARFLAGS so we can build with GNU Make 4.0 Peter Maydell
2013-11-05 19:31 ` Andreas Färber [this message]
2013-11-05 19:36   ` Peter Maydell
2013-12-04  0:33     ` Michael Roth
2013-12-04  0:38       ` Peter Maydell
2013-12-04  1:43         ` Michael Roth
  -- strict thread matches above, loose matches on Subject: below --
2013-10-21 20:03 Peter Maydell
2013-10-22  8:24 ` Peter Maydell
2013-10-22 17:35   ` Ken Moffat
2013-10-22 18:09     ` Ken Moffat
2013-10-22 18:52       ` Ken Moffat
2013-10-22 18:10     ` Peter Maydell
2013-10-22 18:19       ` Ken Moffat
2013-10-23  7:54   ` Paolo Bonzini
2013-11-05 18:04 ` Peter Maydell
2013-11-05 18:45   ` Andreas Färber

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=52794784.2020304@suse.de \
    --to=afaerber@suse.de \
    --cc=aliguori@amazon.com \
    --cc=patches@linaro.org \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=zarniwhoop@ntlworld.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 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).