From: Peter Maydell <peter.maydell@linaro.org>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
qemu-stable <qemu-stable@nongnu.org>,
QEMU Developers <qemu-devel@nongnu.org>,
Patch Tracking <patches@linaro.org>
Subject: Re: [Qemu-devel] [PATCH 0/3] ARM: three easy patches for coverity-reported issues
Date: Tue, 18 Feb 2014 13:05:02 +0000 [thread overview]
Message-ID: <CAFEAcA8px32Bw8sMEx8aKq1jjTpzuWcpe64=gP0L+7xUXc-OqQ@mail.gmail.com> (raw)
In-Reply-To: <530355AB.5020002@suse.de>
On 18 February 2014 12:44, Andreas Färber <afaerber@suse.de> wrote:
> What especially annoys me here is that Peter wants to play on Anthony's
> level on the project but is openly ignoring both our stable releases as
> a concept (we wouldn't need a release in the first place if we don't
> care about it working!) and the procedures decided in his presence at
> QEMU Summit (having maintainer/contributor flag it via Cc: line). If you
> feel the conclusion we reached there is not working out, feel free to
> bring this topic up on the KVM call later today - playing
> Rumpelstilzchen and exempting you from what everyone else is doing is
> not an acceptable solution. Either we all do it this way or we all
> decide on another way. It was not my suggestion, just a proposed
> solution to an issue that affects me, so I'm open to alternatives.
I'm just pointing out (as I do pretty much any time somebody
says "hey you should have cc'd stable") that this workflow
isn't working for me as a contributor or as a submaintainer.
If you can document and define how it's actually supposed to
work and what the policy is for what counts as a bugfix that
should target stable (I couldn't find anything on the wiki)
then that might help. We should probably discuss this on the
call, yes.
thanks
-- PMM
next prev parent reply other threads:[~2014-02-18 13:05 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-17 14:37 [Qemu-devel] [PATCH 0/3] ARM: three easy patches for coverity-reported issues Peter Maydell
2014-02-17 14:37 ` [Qemu-devel] [PATCH 1/3] hw/misc/arm_sysctl: Fix bad boundary check on mb clock accesses Peter Maydell
2014-02-17 14:37 ` [Qemu-devel] [PATCH 2/3] hw/net/stellaris_enet: Avoid unintended sign extension Peter Maydell
2014-02-17 14:37 ` [Qemu-devel] [PATCH 3/3] hw/timer/arm_timer: Avoid array overrun for bad addresses Peter Maydell
2014-02-17 18:59 ` [Qemu-devel] [PATCH 0/3] ARM: three easy patches for coverity-reported issues Paolo Bonzini
2014-02-18 1:02 ` Andreas Färber
2014-02-18 9:46 ` Peter Maydell
2014-02-18 10:13 ` Andreas Färber
2014-02-18 11:09 ` Peter Maydell
2014-02-18 11:16 ` Paolo Bonzini
2014-02-18 11:22 ` Peter Maydell
2014-02-18 11:23 ` Paolo Bonzini
2014-02-18 12:17 ` Alexander Graf
2014-02-18 12:37 ` Peter Maydell
2014-02-18 12:51 ` Alexander Graf
2014-02-18 12:53 ` Andreas Färber
2014-02-18 12:56 ` Alexander Graf
2014-02-18 12:44 ` Andreas Färber
2014-02-18 13:05 ` Peter Maydell [this message]
2014-02-18 13:53 ` Paolo Bonzini
2014-02-21 7:24 ` [Qemu-devel] [Qemu-stable] " Michael Roth
2014-02-21 10:43 ` Paolo Bonzini
2014-02-24 15:41 ` [Qemu-devel] " Peter Maydell
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='CAFEAcA8px32Bw8sMEx8aKq1jjTpzuWcpe64=gP0L+7xUXc-OqQ@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=afaerber@suse.de \
--cc=patches@linaro.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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).