public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH v2 1/1] kernel-2.eclass: Support move of genpatches tarballs from /space/distfiles-local to devspace
Date: Wed, 09 Oct 2019 22:19:49 +0200	[thread overview]
Message-ID: <12b7e760d85b6316c82fac167f57f7cc73fcd4d2.camel@gentoo.org> (raw)
In-Reply-To: <20191009193100.GA29752@woodpecker.gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1542 bytes --]

On Wed, 2019-10-09 at 15:31 -0400, Mike Pagano wrote:
> Thanks for the suggestion. This is version 2
> 
> This change will support moving the genpatches tarballs from /space/distfiles-local to
> the devspace ~developer/public_html/dist/genpatches.
> 
> 
> Signed-off-by: Mike Pagano <mpagano@gentoo.org>
> ---
>  eclass/kernel-2.eclass | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/eclass/kernel-2.eclass b/eclass/kernel-2.eclass
> index c5f35cd3e..4b861beec 100644
> --- a/eclass/kernel-2.eclass
> +++ b/eclass/kernel-2.eclass
> @@ -295,7 +295,9 @@ handle_genpatches() {
>                         UNIPATCH_LIST_GENPATCHES+=" ${DISTDIR}/${tarball}"
>                         debug-print "genpatches tarball: $tarball"
>                 fi
> -               GENPATCHES_URI+=" ${use_cond_start}mirror://gentoo/${tarball}${use_cond_end}"
> +               GENPATCHES_URI+=" ${use_cond_start}https://dev.gentoo.org/~mpagano/dist/genpatches/${tarball}
> +                       https://dev.gentoo.org/~whissi/dist/genpatches/${tarball}
> +                       https://dev.gentoo.org/~alicef/dist/genpatches/${tarball}${use_cond_end}"

Given that yours is the only name I see on woodpecker, do we need to
proactively add all dead URLs in there?  I'd rather have people add them
when they actually going to use them (and I think that would qualify
as the kind of change not needing ml review then).

>         done
>  }
> 
> --
> 2.21.0
> 

-- 
Best regards,
Michał Górny


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 618 bytes --]

  reply	other threads:[~2019-10-09 20:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-09 17:01 [gentoo-dev] [PATCH 1/1] kernel-2.eclass: Support move of genpatches tarballs from /space/distfiles-local to devspace Mike Pagano
2019-10-09 18:26 ` Ulrich Mueller
2019-10-09 19:31   ` [gentoo-dev] [PATCH v2 " Mike Pagano
2019-10-09 20:19     ` Michał Górny [this message]
2019-10-09 23:14       ` [gentoo-dev] [PATCH v3 " Mike Pagano
2019-10-10  8:56         ` Ulrich Mueller
2019-10-10 11:25           ` [gentoo-dev] [PATCH v4 " Mike Pagano
2019-10-11 15:59           ` [gentoo-dev] [PATCH v3 " Thomas Deutschmann
2019-10-12 10:35             ` Ulrich Mueller
2019-10-12 19:04         ` Mike
2019-10-10  1:23 ` [gentoo-dev] [PATCH " Alec Warner
2019-10-10 10:04   ` Mike Pagano
2019-10-10 16:15     ` Mikle Kolyada
2019-10-11 18:28     ` Alec Warner
2019-10-11 20:52       ` Mike Pagano

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=12b7e760d85b6316c82fac167f57f7cc73fcd4d2.camel@gentoo.org \
    --to=mgorny@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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