qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: qemu-devel@nongnu.org
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
	"Pierrick Bouvier" <pierrick.bouvier@linaro.org>
Subject: [PULL 04/10] docs/devel: fix duplicate line
Date: Wed, 11 Sep 2024 07:46:39 +0100	[thread overview]
Message-ID: <20240911064645.357592-5-alex.bennee@linaro.org> (raw)
In-Reply-To: <20240911064645.357592-1-alex.bennee@linaro.org>

I guess the same change came in via two patch series. Remove the
repetition.

Fixes: 2a851fca9f (docs/devel: remind developers to run CI container pipeline when updating images)
Reviewed-by: Pierrick Bouvier <pierrick.bouvier@linaro.org>
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Message-Id: <20240910173900.4154726-5-alex.bennee@linaro.org>

diff --git a/docs/devel/testing/main.rst b/docs/devel/testing/main.rst
index e9921a4b10..09725e8ea9 100644
--- a/docs/devel/testing/main.rst
+++ b/docs/devel/testing/main.rst
@@ -500,12 +500,6 @@ first to contribute the mapping to the ``libvirt-ci`` project:
    `CI <https://www.qemu.org/docs/master/devel/ci.html>`__ documentation
    page on how to trigger gitlab CI pipelines on your change.
 
- * Please also trigger gitlab container generation pipelines on your change
-   for as many OS distros as practical to make sure that there are no
-   obvious breakages when adding the new pre-requisite. Please see
-   `CI <https://www.qemu.org/docs/master/devel/ci.html>`__ documentation
-   page on how to trigger gitlab CI pipelines on your change.
-
 For enterprise distros that default to old, end-of-life versions of the
 Python runtime, QEMU uses a separate set of mappings that work with more
 recent versions.  These can be found in ``tests/lcitool/mappings.yml``.
-- 
2.39.2



  parent reply	other threads:[~2024-09-11  6:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-11  6:46 [PULL 00/10] testing and gdbstub updates Alex Bennée
2024-09-11  6:46 ` [PULL 01/10] tests/docker: remove debian-armel-cross Alex Bennée
2024-09-11  6:46 ` [PULL 02/10] tests/docker: update debian i686 and mipsel images to bookworm Alex Bennée
2024-09-11  6:46 ` [PULL 03/10] tests/docker: use debian-all-test-cross for mips64el tests Alex Bennée
2024-09-11  6:46 ` Alex Bennée [this message]
2024-09-11  6:46 ` [PULL 05/10] scripts/ci: update the gitlab-runner playbook Alex Bennée
2024-09-11  6:46 ` [PULL 06/10] gdbstub: Use specific MMU index when probing MTE addresses Alex Bennée
2024-09-11  6:46 ` [PULL 07/10] gdbstub: Add support for MTE in system mode Alex Bennée
2024-09-11  6:46 ` [PULL 08/10] tests/guest-debug: Support passing arguments to the GDB test script Alex Bennée
2024-09-11  6:46 ` [PULL 09/10] tests/tcg/aarch64: Improve linker script organization Alex Bennée
2024-09-11  6:46 ` [PULL 10/10] tests/tcg/aarch64: Extend MTE gdbstub tests to system mode Alex Bennée
2024-09-11 18:27 ` [PULL 00/10] testing and gdbstub updates 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=20240911064645.357592-5-alex.bennee@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=pierrick.bouvier@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).