From: "Andreas Färber" <afaerber@suse.de>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Anthony Liguori <aliguori@amazon.com>
Subject: Re: [Qemu-devel] [PULL 0/6] target-arm queue
Date: Thu, 31 Oct 2013 18:14:38 +0100 [thread overview]
Message-ID: <52728FFE.4000802@suse.de> (raw)
In-Reply-To: <CAFEAcA9p=R5x4NhOE3tfhecEAMHjmQ3wDJtH_G2E_qVoyYupog@mail.gmail.com>
Am 31.10.2013 16:16, schrieb Peter Maydell:
> On 31 October 2013 14:36, Andreas Färber <afaerber@suse.de> wrote:
>> Am 31.10.2013 15:31, schrieb Peter Maydell:
>>> On 31 October 2013 14:18, Andreas Färber <afaerber@suse.de> wrote:
>>>> Peter, since I had picked up the first two patches into my still pending
>>>> qom-next pull, as per the QEMU Summit discussion those patches should've
>>>> gotten an Acked-by.
>>>
>>> Hmm? I don't recall this part of the discussion. If you want the
>>> patches to have an Acked-by from you you need to send mail
>>> to the list with an Acked-by line.
>>
>> No, I added a Signed-off-by.
>
> I checked my mail and the only thing I can find in reply to those
> patches is a note from you saying you added them to your queue.
Right, and as such they got a Signed-off-by, which should've been
visible in the link I usually add. Here's the pull messages you
should've been cc'ed on:
http://patchwork.ozlabs.org/patch/281630/
http://patchwork.ozlabs.org/patch/281575/
I don't see why I should reply with a Reviewed-by when I pick up patches
- again, same discussion as at QEMU Summit.
>> It was clearly stated that a Reviewed-by
>> needs to be explicitly sent as reply but that "looks okay" should in
>> exactly such a case where sender=submaintainer should be recorded as
>> Acked-by, and Sob is certainly stronger than Acked-by. Cf. minutes.
>
> ...but you're not the submaintainer here so I don't think this applies.
It does, because you are the patch author and the ARM submaintainer
sending the pull.
> The point about the kernel practice as I understood it was that
> the kernel folks treat acked-by at about the same level of review as
> "looks ok to me" (ie, very little), not that there's some obligation to
> treat any informal 'looks ok' note as an acked-by. I'm in full agreement
> with Anthony that if you want a tag to appear you should send it
> properly.
If Anthony had been and would be more responsive as to why he didn't
pull the queue containing these patches with two different Sobs, we
wouldn't be having this conversation in the first place. Or had you not
gone on vacation or sent another pull before etc. etc.
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2013-10-31 17:14 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-25 18:07 [Qemu-devel] [PULL 0/6] target-arm queue Peter Maydell
2013-10-25 18:07 ` [Qemu-devel] [PULL 1/6] hw/arm/boot: Make user not specifying a kernel not an error Peter Maydell
2013-10-25 18:07 ` [Qemu-devel] [PULL 2/6] hw/arm: Tidy up conditional calls to arm_load_kernel Peter Maydell
2013-10-25 18:07 ` [Qemu-devel] [PULL 3/6] target-arm: Add CP15 VBAR support Peter Maydell
2013-10-25 18:07 ` [Qemu-devel] [PULL 4/6] target-arm: sort TCG cpreg list by KVM-style 64 bit ID number Peter Maydell
2013-10-25 18:07 ` [Qemu-devel] [PULL 5/6] target-arm: fix sorting issue of KVM cpreg list Peter Maydell
2013-10-25 18:07 ` [Qemu-devel] [PULL 6/6] integrator: fix Linux boot failure by emulating dbg region Peter Maydell
2013-10-31 14:02 ` [Qemu-devel] [PULL 0/6] target-arm queue Edgar E. Iglesias
2013-10-31 14:18 ` Andreas Färber
2013-10-31 14:21 ` Anthony Liguori
2013-10-31 14:31 ` Peter Maydell
2013-10-31 14:36 ` Andreas Färber
2013-10-31 14:39 ` Anthony Liguori
2013-10-31 14:45 ` Andreas Färber
2013-10-31 14:54 ` Anthony Liguori
2013-10-31 15:04 ` Anthony Liguori
2013-10-31 16:52 ` Andreas Färber
2013-10-31 16:54 ` Anthony Liguori
2013-10-31 17:10 ` Andreas Färber
2013-10-31 17:02 ` Peter Maydell
2013-10-31 17:15 ` Peter Maydell
2013-10-31 18:55 ` Anthony Liguori
2013-10-31 15:16 ` Peter Maydell
2013-10-31 17:14 ` Andreas Färber [this message]
2013-10-31 17:18 ` Peter Maydell
2013-10-31 17:27 ` Andreas Färber
2013-10-31 17:51 ` Peter Maydell
2013-10-31 18:58 ` Anthony Liguori
2013-10-31 22:13 ` Edgar E. Iglesias
-- strict thread matches above, loose matches on Subject: below --
2014-03-19 12:05 Peter Maydell
2014-03-19 13:33 ` Peter Maydell
2016-07-07 13:48 Peter Maydell
2016-07-11 10:16 ` Peter Maydell
2018-07-30 14:17 Peter Maydell
2018-07-30 18:11 ` Peter Maydell
2018-10-29 15:34 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=52728FFE.4000802@suse.de \
--to=afaerber@suse.de \
--cc=aliguori@amazon.com \
--cc=edgar.iglesias@gmail.com \
--cc=peter.maydell@linaro.org \
--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.