[Buildroot] [PATCH 1 of 2 v2] manual: github commits should be specified in full
Thomas De Schampheleire
patrickdepinguin at gmail.com
Sat Nov 2 13:22:17 UTC 2013
Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire at gmail.com>
---
v2: remove parentheses around 'full' (comment Samuel)
docs/manual/adding-packages-tips.txt | 5 ++---
1 files changed, 2 insertions(+), 3 deletions(-)
diff --git a/docs/manual/adding-packages-tips.txt b/docs/manual/adding-packages-tips.txt
--- a/docs/manual/adding-packages-tips.txt
+++ b/docs/manual/adding-packages-tips.txt
@@ -44,7 +44,7 @@ However, it is possible to download tarb
on github.
------------------------
-FOO_VERSION = v1.0 # tag or (abbreviated) commit ID
+FOO_VERSION = v1.0 # tag or full commit ID
FOO_SITE = http://github.com/<user>/<package>/tarball/$(FOO_VERSION)
------------------------
@@ -53,5 +53,4 @@ FOO_SITE = http://github.com/<user>/<pac
- The tarball name generated by github matches the default one from
Buildroot (e.g.: +foo-1234567.tar.gz+),
so it is not necessary to specify it in the +.mk+ file.
-- When using a commit ID as version, usually the first 7 characters of
- the SHA1 are enough.
+- When using a commit ID as version, you should use the full 40 hex characters.
More information about the buildroot
mailing list