All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "QEMU Developers" <qemu-devel@nongnu.org>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	"Richard Henderson" <richard.henderson@linaro.org>,
	"Kevin Wolf" <kwolf@redhat.com>, "John Snow" <jsnow@redhat.com>,
	"Daniel P. Berrange" <berrange@redhat.com>
Subject: Re: no more pullreq processing til February
Date: Fri, 27 Jan 2023 10:30:28 +0100	[thread overview]
Message-ID: <87cz705npn.fsf@pond.sub.org> (raw)
In-Reply-To: <CAFEAcA8v8hrqkFemdT5x_O5_mdps4wpdRCoVAfts+oVJj_qTVw@mail.gmail.com> (Peter Maydell's message of "Thu, 26 Jan 2023 13:22:32 +0000")

If this backpressure leads us to less waste of time & energy (close &
personal: faster make check), then I <3 gitlab!



      parent reply	other threads:[~2023-01-27  9:31 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-26 13:22 no more pullreq processing til February Peter Maydell
2023-01-26 13:52 ` Eldon Stegall
2023-01-26 14:13   ` Alex Bennée
2023-01-26 14:27     ` Peter Maydell
2023-01-26 14:38     ` Daniel P. Berrangé
2023-01-26 18:41       ` Eldon Stegall
2023-01-27  9:53         ` Daniel P. Berrangé
2023-01-26 14:18   ` Daniel P. Berrangé
2023-01-26 14:30     ` Daniel P. Berrangé
2023-01-27  8:50       ` Gerd Hoffmann
2023-01-26 13:57 ` Alex Bennée
2023-01-26 14:07   ` Daniel Henrique Barboza
2023-01-26 14:27     ` Daniel P. Berrangé
2023-01-26 14:35   ` Daniel P. Berrangé
2023-01-26 14:41     ` Peter Maydell
2023-01-26 18:17       ` Thomas Huth
2023-01-26 20:49         ` Alex Bennée
2023-01-26 14:25 ` Stefan Hajnoczi
2023-01-26 14:28   ` Peter Maydell
2023-01-27  7:36     ` Thomas Huth
2023-01-27 12:39     ` Kevin Wolf
2023-01-27 12:47       ` Daniel P. Berrangé
2023-01-27 13:11       ` Peter Maydell
2023-01-27 13:12         ` Peter Maydell
2023-02-01 16:18       ` Peter Maydell
2023-01-27  9:30 ` Markus Armbruster [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=87cz705npn.fsf@pond.sub.org \
    --to=armbru@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=berrange@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.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.