From: Thomas De Schampheleire <patrickdepinguin@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] linux: clarify help text for 'custom tarball'
Date: Fri, 16 Jan 2015 09:07:05 +0100 [thread overview]
Message-ID: <1421395625-2672-1-git-send-email-patrickdepinguin@gmail.com> (raw)
From: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>
The help text for Linux option 'Custom tarball' only refers to ftp or
http tarballs, while in reality file or scp protocols are also
supported.
Triggered by a recent support question, update the help text to clarify
this.
Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>
---
linux/Config.in | 9 +++++++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/linux/Config.in b/linux/Config.in
index a670802..1df0a49 100644
--- a/linux/Config.in
+++ b/linux/Config.in
@@ -48,8 +48,13 @@ config BR2_LINUX_KERNEL_CUSTOM_VERSION
config BR2_LINUX_KERNEL_CUSTOM_TARBALL
bool "Custom tarball"
help
- This option allows to specify the http or ftp location of a
- specific kernel source tarball
+ This option allows to specify a URL pointing to a kernel source
+ tarball. This URL can use any protocol recognized by Buildroot,
+ like http://, ftp://, file:// or scp://.
+
+ When pointing to a local tarball using file://, you may want to
+ use a make variable like $(TOPDIR) to reference the root of the
+ Buildroot tree.
config BR2_LINUX_KERNEL_CUSTOM_GIT
bool "Custom Git repository"
--
1.8.5.1
next reply other threads:[~2015-01-16 8:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-16 8:07 Thomas De Schampheleire [this message]
2015-01-16 21:34 ` [Buildroot] [PATCH] linux: clarify help text for 'custom tarball' Thomas Petazzoni
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=1421395625-2672-1-git-send-email-patrickdepinguin@gmail.com \
--to=patrickdepinguin@gmail.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