From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Andre McCurdy <armccurdy@gmail.com>,
Mark Hatle <mark.hatle@windriver.com>
Cc: bitbake-devel <bitbake-devel@lists.openembedded.org>,
Fabien Proriol <fabien.proriol@jdsu.com>,
fabien.proriolpatch@kazoe.org
Subject: Re: [PATCH] bb.fetch.git: add a way to avoid git protocol, and force http or https mirrors
Date: Tue, 25 Jul 2017 23:19:21 +0100 [thread overview]
Message-ID: <1501021161.22282.138.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAJ86T=UW4gzF_CVhVMFdRCJsm3Nc6ETB9Acj=CUDzv96yUDg+g@mail.gmail.com>
On Tue, 2017-07-25 at 12:30 -0700, Andre McCurdy wrote:
> On Tue, Jul 25, 2017 at 7:43 AM, Mark Hatle <mark.hatle@windriver.com
> > wrote:
> > Won't the following work:
> >
> > PREMIRRORS_append = " \
> > git://.*/.* git://HOST/PATH;protocol=https \n \
> > git://.*/.* git://HOST/PATH;protocol=http \n \
> > "
> Thanks! Yes, that does work. It's the first time I've ever seen HOST
> or PATH being used as mirror replacement patterns. Useful to know.
>
> Would a patch adding something similar to the default MIRRORS (ie try
> http[s] as a fallback if the git protocol fails) be acceptable in
> upstream oe-core?
Yes, I'd take such a patch. I'd love to have this better documented.
Cheers,
Richard
next prev parent reply other threads:[~2017-07-25 22:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-31 13:18 [PATCH] bb.fetch.git: add a way to avoid git protocol, and force http or https mirrors fabien.proriolpatch
2016-05-31 13:39 ` Olof Johansson
2016-05-31 13:50 ` Richard Purdie
2017-07-24 21:04 ` Andre McCurdy
2017-07-25 14:43 ` Mark Hatle
2017-07-25 19:30 ` Andre McCurdy
2017-07-25 22:19 ` Richard Purdie [this message]
2017-07-26 12:58 ` Mark Hatle
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=1501021161.22282.138.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=armccurdy@gmail.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=fabien.proriol@jdsu.com \
--cc=fabien.proriolpatch@kazoe.org \
--cc=mark.hatle@windriver.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 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.