From: "Alex Bennée" <alex.bennee@linaro.org>
To: Willian Rampazzo <wrampazz@redhat.com>
Cc: "Fam Zheng" <fam@euphon.net>,
"Daniel Berrange" <berrange@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Cleber Rosa Junior" <crosa@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Aurelien Jarno" <aurelien@aurel32.net>
Subject: Re: [PATCH v1 0/9] testing/next (docs, hexagon, cfi, docker)
Date: Sun, 07 Mar 2021 17:29:15 +0000 [thread overview]
Message-ID: <87r1kqlvnp.fsf@linaro.org> (raw)
In-Reply-To: <CAKJDGDboytn0H7fQfHZEbuUkfoB+GaTqwU9FcASnxoQECAom4Q@mail.gmail.com>
Willian Rampazzo <wrampazz@redhat.com> writes:
> On Fri, Mar 5, 2021 at 6:31 AM Alex Bennée <alex.bennee@linaro.org> wrote:
>>
>> Hi,
>>
>> Another week another testing/next roll. The series includes a couple
>> of my proposed documentation tweaks (including the re-org of the devel
>> manual). We also enable testing for the hexagon linux-user target to
>> avoid bitrot. I've documented the process for manually updating the
>> registry at:
>>
>> https://wiki.qemu.org/Testing/DockerBuild#The_GitLab_Registry
>>
>
> I see a mix of valid/invalid URLs, like `registry.gitlab.example.com`
> and then `registry.gitlab.com`. For consistency, my suggestion is to
> use either the example URL or a valid URL mentioning that is an
> example for a specific docker image.
Oops bad copy/paste from my shell history. Fixed now.
--
Alex Bennée
prev parent reply other threads:[~2021-03-07 17:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-05 9:23 [PATCH v1 0/9] testing/next (docs, hexagon, cfi, docker) Alex Bennée
2021-03-05 9:23 ` [PATCH v1 1/9] docs/devel: re-organise the developers guide into sections Alex Bennée
2021-03-05 9:40 ` Philippe Mathieu-Daudé
2021-03-05 13:37 ` Alex Bennée
2021-03-05 9:23 ` [PATCH v1 2/9] docs/system: add a gentle prompt for the complexity to come Alex Bennée
2021-03-05 9:23 ` [PATCH v1 3/9] tests/docker: add a test-tcg for building then running check-tcg Alex Bennée
2021-03-05 9:41 ` Philippe Mathieu-Daudé
2021-03-05 9:23 ` [PATCH v1 4/9] docker: Add Hexagon image Alex Bennée
2021-03-05 9:23 ` [PATCH v1 5/9] tests/tcg: Use Hexagon Docker image Alex Bennée
2021-03-05 9:23 ` [PATCH v1 6/9] gitlab: add build-user-hexagon test Alex Bennée
2021-03-05 9:43 ` Philippe Mathieu-Daudé
2021-03-05 15:37 ` Wainer dos Santos Moschetta
2021-03-05 9:23 ` [PATCH v1 7/9] gitlab-ci.yml: Allow custom # of parallel linkers Alex Bennée
2021-03-05 9:23 ` [PATCH v1 8/9] gitlab-ci.yml: Add jobs to test CFI flags Alex Bennée
2021-03-05 9:43 ` Philippe Mathieu-Daudé
2021-03-05 9:23 ` [PATCH v1 9/9] tests/docker: Use --arch-only when building Debian cross image Alex Bennée
2021-03-05 9:42 ` [PATCH v1 0/9] testing/next (docs, hexagon, cfi, docker) no-reply
2021-03-05 19:37 ` Willian Rampazzo
2021-03-07 17:29 ` Alex Bennée [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=87r1kqlvnp.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=aurelien@aurel32.net \
--cc=berrange@redhat.com \
--cc=crosa@redhat.com \
--cc=f4bug@amsat.org \
--cc=fam@euphon.net \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=wrampazz@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).