From: Gerd Hoffmann <kraxel@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Kevin Wolf <kwolf@redhat.com>, Jason Wang <jasowang@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Markus Armbruster <armbru@redhat.com>
Subject: Re: please try to avoid sending pullreqs late on release-candidate day
Date: Tue, 21 Jul 2020 23:16:26 +0200 [thread overview]
Message-ID: <20200721211626.3kepsmdi2n6tkigw@sirius.home.kraxel.org> (raw)
In-Reply-To: <CAFEAcA9+9ZQY2CxZ9V4bZrkAGR5eUapbwSk6sNyFGyyd39Y=1Q@mail.gmail.com>
On Tue, Jul 21, 2020 at 04:56:25PM +0100, Peter Maydell wrote:
> It is not helpful if everybody sends their pullrequests late
> on the Tuesday afternoon, as there just isn't enough time in the
> day to merge test and apply them all before I have to cut the tag.
> Please, if you can, try to send pullrequests earlier, eg Monday.
I usually try, but it didn't work out this time due to patches coming
in late ...
Speaking of testing: What is the state of gitlab ci? How much of the
testing has been migrated over? I've noticed I can push branches and
tags to a qemu fork @ gitlab.com and gitlab ci runs a bunch of tests.
What is the best way to indicate that the tag did pass gitlab ci
already? Maybe simply send a pull request with gitlab.com url?
take care,
Gerd
next prev parent reply other threads:[~2020-07-21 21:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-21 15:56 please try to avoid sending pullreqs late on release-candidate day Peter Maydell
2020-07-21 21:16 ` Gerd Hoffmann [this message]
2020-07-22 8:05 ` Peter Maydell
2020-07-22 3:34 ` Jason Wang
2020-07-22 9:36 ` Kevin Wolf
2020-07-22 11:50 ` Peter Maydell
2020-07-22 12:16 ` Alex Bennée
2020-07-23 6:28 ` Markus Armbruster
2020-07-23 10:26 ` Philippe Mathieu-Daudé
2020-07-23 11:12 ` Markus Armbruster
2020-07-23 16:36 ` Alex Bennée
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=20200721211626.3kepsmdi2n6tkigw@sirius.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=armbru@redhat.com \
--cc=jasowang@redhat.com \
--cc=kwolf@redhat.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 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).