Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Bjørn Forsman" <bjorn.forsman@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] docs: fix $(PKG)_SITE_METHOD names (UPPER CASE => lower case)
Date: Tue,  1 Feb 2011 23:22:39 +0100	[thread overview]
Message-ID: <1296598960-356-1-git-send-email-bjorn.forsman@gmail.com> (raw)

Currently, the documentation says $(PKG)_SITE_METHOD should have upper
case names such as SVN or GIT, but the implementation only accepts lower
case svn or git. This fixes the documentation.

Signed-off-by: Bj?rn Forsman <bjorn.forsman@gmail.com>
---
 docs/buildroot.html |   14 +++++++-------
 1 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/docs/buildroot.html b/docs/buildroot.html
index 36297e0..de6b1d7 100644
--- a/docs/buildroot.html
+++ b/docs/buildroot.html
@@ -1060,17 +1060,17 @@ $(eval $(call GENTARGETS,package,libfoo,host))
 
       <li><code>LIBFOO_SITE_METHOD</code> may contain the method to
       fetch the package source code. It can either
-      be <code>WGET</code> (for normal FTP/HTTP downloads of
-      tarballs), <code>SVN</code> or <code>GIT</code>. When not
+      be <code>wget</code> (for normal FTP/HTTP downloads of
+      tarballs), <code>svn</code> or <code>git</code>. When not
       specified, it is guessed from the URL given
       in <code>LIBFOO_SITE</code>: <code>git://</code>
-      and <code>svn://</code> URLs will use the <code>GIT</code>
-      and <code>SVN</code> methods respectively. All other URL-types
-      will use the <code>WGET</code> method. So for example, in the
+      and <code>svn://</code> URLs will use the <code>git</code>
+      and <code>svn</code> methods respectively. All other URL-types
+      will use the <code>wget</code> method. So for example, in the
       case of a package whose source code is available through
       Subversion repository on HTTP, one <i>must</i>
-      specifiy <code>LIBFOO_SITE_METHOD=SVN</code>. For <code>SVN</code>
-      and <code>GIT</code> methods, what Buildroot does is a
+      specifiy <code>LIBFOO_SITE_METHOD=svn</code>. For <code>svn</code>
+      and <code>git</code> methods, what Buildroot does is a
       checkout/clone of the repository which is then tarballed and
       stored into the download cache. Next builds will not
       checkout/clone again, but will use the tarball
-- 
1.7.1

             reply	other threads:[~2011-02-01 22:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-01 22:22 Bjørn Forsman [this message]
2011-02-01 22:22 ` [Buildroot] [PATCH 2/2] docs: add missing info about Bazaar (bzr) download method Bjørn Forsman
2011-02-06 16:51   ` Bjørn Forsman
2011-02-06 18:03   ` Thomas Petazzoni
2011-02-06 18:42     ` Daniel Nyström
2011-02-06 16:49 ` [Buildroot] [PATCH 1/2] docs: fix $(PKG)_SITE_METHOD names (UPPER CASE => lower case) Bjørn Forsman
2011-02-06 18:03 ` 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=1296598960-356-1-git-send-email-bjorn.forsman@gmail.com \
    --to=bjorn.forsman@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