From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] wandboard: Use HTTP for accessing Linux kernel and U-Boot git repos
Date: Tue, 28 Jun 2016 08:28:53 +0000 [thread overview]
Message-ID: <1467102471.3231.17.camel@synopsys.com> (raw)
In-Reply-To: <87eg7hpvm7.fsf@dell.be.48ers.dk>
Hi Peter,
On Tue, 2016-06-28 at 10:26 +0200, Peter Korsgaard wrote:
> >
> > >
> > > >
> > > > >
> > > > > >
> > > > > > "Alexey" == Alexey Brodkin <Alexey.Brodkin@synopsys.com> writes:
> ?> Quite often these days Git ports are blocked by firewalls
> ?> [this is especially true in corporate environment] so switching
> ?> to common HTTP(s) is a safe and pretty convenient move.
>
> ?> Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com>
> ?> Cc: Stephan Hoffmann <sho@relinux.de>
> ?> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> ?> Cc: Sergio Prado <sergio.prado@e-labworks.com>
> ?> Cc: Peter Korsgaard <peter@korsgaard.com>
> ?> ---
> ?>??configs/wandboard_defconfig | 4 ++--
> ?>??1 file changed, 2 insertions(+), 2 deletions(-)
>
> Committed, thanks.
>
> ?> -BR2_TARGET_UBOOT_CUSTOM_REPO_URL="git://git.denx.de/u-boot.git"
> ?> +BR2_TARGET_UBOOT_CUSTOM_REPO_URL="http://git.denx.de/u-boot.git"
>
> This is actually just the 2015.07 release:
>
> git describe 33711bdd4a4dce942fb5ae85a68899a8357bdd94
> v2015.07
>
> So I've changed it to use the release tarball instead.
Thanks for that.
Now I'm trying to get Wandboard working from the most recent upstream
kernel and U-Boot. If it all works I'll update that defconfig again :)
-Alexey
next prev parent reply other threads:[~2016-06-28 8:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-28 7:45 [Buildroot] [PATCH] wandboard: Use HTTP for accessing Linux kernel and U-Boot git repos Alexey Brodkin
2016-06-28 8:26 ` Peter Korsgaard
2016-06-28 8:28 ` Alexey Brodkin [this message]
2016-06-28 8:57 ` Peter Korsgaard
2016-07-04 9:54 ` Alexey Brodkin
2016-07-04 12:41 ` Peter Korsgaard
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=1467102471.3231.17.camel@synopsys.com \
--to=alexey.brodkin@synopsys.com \
--cc=buildroot@busybox.net \
/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