From: Thomas Huth <thuth@redhat.com>
To: QEMU Developers <qemu-devel@nongnu.org>
Subject: Please update your QEMU branches to master if using gitlab.com
Date: Thu, 2 Jun 2022 11:07:56 +0200 [thread overview]
Message-ID: <2f587382-a77d-740a-b7b7-08d6bf5a5884@redhat.com> (raw)
Hi all,
just a reminder: Please note that gitlab.com introduced limits on the
available CI minutes since yesterday [1]. So if you are using gitlab for
storing your QEMU branches, please make sure that you update your branches
to the very latest version of the qemu-project's master branch - this now
contains some patches that prevent the CI from running by default when
pushing branches to gitlab, so you should not accidentally run out of CI
minutes anymore. For details, please refer to [2].
HTH,
Thomas
[1] https://about.gitlab.com/blog/2021/11/11/public-project-minute-limits/
[2] https://gitlab.com/qemu-project/qemu/-/commit/28357dc525b4798
reply other threads:[~2022-06-02 9:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=2f587382-a77d-740a-b7b7-08d6bf5a5884@redhat.com \
--to=thuth@redhat.com \
--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).