From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Unable to download Linux "master" on 2018.05 release
Date: Tue, 17 Jul 2018 14:48:24 +0200 [thread overview]
Message-ID: <20180717144824.223ae7f2@windsurf> (raw)
In-Reply-To: <c67d510c5c14ddb0f5f4661317f1801e921eedc7.camel@synopsys.com>
Hello,
On Tue, 17 Jul 2018 12:43:53 +0000, Evgeniy Didin wrote:
> Hello everyone,
>
> Recently I have faced with an error trying to download "master" version of Torvalds Linux branch. I am using 2018.05 tag of buildroot.
> Here is part of my defconfig:
> -----------------------------------------------8<----------------------------------------------------------------------------------------------
> BR2_LINUX_KERNEL=y
> BR2_LINUX_KERNEL_CUSTOM_GIT=y
> BR2_LINUX_KERNEL_CUSTOM_REPO_URL="https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git"
> BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION="master"
> BR2_LINUX_KERNEL_DEFCONFIG="hsdk"
> ----------------------------------------------->8----------------------------------------------------------------------------------------------
Fetching from a Git branch name is not supported. It used to work by
accident, but now it no longer works at all. It's a bad thing to do,
because Buildroot will never refetch that branch once it has cached a
tarball linux-master.tar.gz.
However, it is on our TODO list to provide an explicit error message
when this situation arise.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2018-07-17 12:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-17 12:43 [Buildroot] Unable to download Linux "master" on 2018.05 release Evgeniy Didin
2018-07-17 12:48 ` Thomas Petazzoni [this message]
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=20180717144824.223ae7f2@windsurf \
--to=thomas.petazzoni@bootlin.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