All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aaron Conole <aconole@redhat.com>
To: David Marchand <david.marchand@redhat.com>
Cc: dev@dpdk.org,  stable@dpdk.org,
	 Michael Santana <maicolgabriel@hotmail.com>
Subject: Re: [PATCH] ci: point at GitHub mirror.
Date: Wed, 05 Mar 2025 09:59:10 -0500	[thread overview]
Message-ID: <f7tsenr4j7l.fsf@redhat.com> (raw)
In-Reply-To: <20250304155036.383468-1-david.marchand@redhat.com> (David Marchand's message of "Tue, 4 Mar 2025 16:50:36 +0100")

David Marchand <david.marchand@redhat.com> writes:

> We face some random failures accessing dpdk.org git when running GHA.
> Point at GitHub hosted mirror.
>
> Cc: stable@dpdk.org
>
> Signed-off-by: David Marchand <david.marchand@redhat.com>
> ---

Thanks - this change makes a lot of sense to me.  I was going to say we
can use the ``GITHUB_REPOSITORY`` variable, but the problem with that is
that it will pull references to the local users repo instead.  I guess
there isn't actually a good reference to a 'source of truth' that is
predefined.

Acked-by: Aaron Conole <aconole@redhat.com>

>  .github/workflows/build.yml | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/.github/workflows/build.yml b/.github/workflows/build.yml
> index 183b0b1999..e98a60a852 100644
> --- a/.github/workflows/build.yml
> +++ b/.github/workflows/build.yml
> @@ -11,7 +11,7 @@ defaults:
>  
>  env:
>    REF_GIT_BRANCH: main
> -  REF_GIT_REPO: https://dpdk.org/git/dpdk
> +  REF_GIT_REPO: https://github.com/DPDK/dpdk
>    REF_GIT_TAG: v24.11
>  
>  jobs:


  parent reply	other threads:[~2025-03-05 14:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-04 15:50 [PATCH] ci: point at GitHub mirror David Marchand
2025-03-04 21:57 ` Patrick Robb
2025-03-05 14:59 ` Aaron Conole [this message]
2025-03-06 17:08 ` David Marchand

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=f7tsenr4j7l.fsf@redhat.com \
    --to=aconole@redhat.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=maicolgabriel@hotmail.com \
    --cc=stable@dpdk.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.