qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Aleksandar Markovic <aleksandar.m.mail@gmail.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	"Stefan Hajnoczi" <stefanha@redhat.com>,
	"Cleber Rosa" <crosa@redhat.com>,
	"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [RFC] Use of the Nacked-by tag by CI scripts
Date: Mon, 9 Dec 2019 11:37:13 +0100	[thread overview]
Message-ID: <efe5a839-96a6-b80f-1452-bb43c7bc3ebd@redhat.com> (raw)
In-Reply-To: <CAL1e-=iRWsWde18AffTOwTesAbGcb5fZWeRytaOsHg5iCQpBgA@mail.gmail.com>

On 09/12/19 11:12, Aleksandar Markovic wrote:
> I'm afraid this would be opening a Pandora's box. For such rare cases, a
> message from a person: "Please hold on this patch until I am back from
> vacation.", "Please wait until I merge my series acting on the same
> files", or similar, would perfectly do the job, as it did in the past.

The point is when you don't see the patch until it gets in a pull
request.  It's not particularly common so I'm okay with no change (and I
agree that Philippe's patch, as is, doesn't solve *this* particular
case) but I also don't see this as causing problems in the future.

Paolo



      reply	other threads:[~2019-12-09 10:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-09  8:44 [RFC] Use of the Nacked-by tag by CI scripts Philippe Mathieu-Daudé
2019-12-09  9:28 ` Aleksandar Markovic
2019-12-09  9:36   ` Paolo Bonzini
2019-12-09 10:12     ` Aleksandar Markovic
2019-12-09 10:37       ` Paolo Bonzini [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=efe5a839-96a6-b80f-1452-bb43c7bc3ebd@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=aleksandar.m.mail@gmail.com \
    --cc=alex.bennee@linaro.org \
    --cc=crosa@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@redhat.com \
    --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 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).