All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony PERARD <anthony.perard@vates.tech>
To: Javi Merino <javi.merino@cloud.com>
Cc: xen-devel@lists.xenproject.org,
	Doug Goldstein <cardoe@cardoe.com>,
	Stefano Stabellini <sstabellini@kernel.org>
Subject: Re: [XEN PATCH v1 1/3] automation: Fix URL to the gitlab container registry documentation
Date: Thu, 17 Oct 2024 17:02:49 +0000	[thread overview]
Message-ID: <ZxFDN0rRfsg0iNBj@l14> (raw)
In-Reply-To: <5ebb776792a345724b43b0843aa41c21febcc843.1729170005.git.javi.merino@cloud.com>

On Thu, Oct 17, 2024 at 05:20:19PM +0100, Javi Merino wrote:
> The gitlab documentation is now at
> https://docs.gitlab.com/ee/administration/packages/container_registry.html

This link seems to be for self-managed instance of gitlab, but the link
in the patch looks fine.

> Signed-off-by: Javi Merino <javi.merino@cloud.com>

The patch description could be removed, so:
Reviewed-by: Anthony PERARD <anthony.perard@vates.tech>

Thanks,

> ---
>  automation/build/README.md | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/automation/build/README.md b/automation/build/README.md
> index bd0c0e041804..ecc898680c91 100644
> --- a/automation/build/README.md
> +++ b/automation/build/README.md
> @@ -110,7 +110,7 @@ make -C automation/build opensuse/tumbleweed-x86_64 PUSH=1
>  
>  [BuildKit]: https://docs.docker.com/build/buildkit/
>  [registry]: https://gitlab.com/xen-project/xen/container_registry
> -[registry help]: https://gitlab.com/help/user/project/container_registry
> +[registry help]: https://docs.gitlab.com/ee/user/packages/container_registry/
>  
>  
>  Building/Running container for a different architecture

-- 

Anthony Perard | Vates XCP-ng Developer

XCP-ng & Xen Orchestra - Vates solutions

web: https://vates.tech


  reply	other threads:[~2024-10-17 17:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-17 16:20 [XEN PATCH v1 0/3] CI: Upgrade the Fedora container and fix build failure Javi Merino
2024-10-17 16:20 ` [XEN PATCH v1 1/3] automation: Fix URL to the gitlab container registry documentation Javi Merino
2024-10-17 17:02   ` Anthony PERARD [this message]
2024-10-18  2:01     ` Stefano Stabellini
2024-10-17 16:20 ` [XEN PATCH v1 2/3] ocaml/libs: Fill build failure due to unused variable in ocaml macro Javi Merino
2024-10-17 17:47   ` Andrew Cooper
2024-10-17 18:08     ` Andrew Cooper
2024-10-18  7:55     ` Christian Lindig
2024-10-18  8:50     ` Javi Merino
2024-10-18  9:47       ` Andrew Cooper
2024-10-17 16:20 ` [XEN PATCH v1 3/3] CI: Refresh and upgrade the Fedora container Javi Merino
2024-10-17 17:03   ` Anthony PERARD
2024-10-18  2:00     ` Stefano Stabellini

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=ZxFDN0rRfsg0iNBj@l14 \
    --to=anthony.perard@vates.tech \
    --cc=cardoe@cardoe.com \
    --cc=javi.merino@cloud.com \
    --cc=sstabellini@kernel.org \
    --cc=xen-devel@lists.xenproject.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.