All of lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] toolchain-external: clarify external toolchain description
Date: Tue, 17 Feb 2015 13:48:05 +0200	[thread overview]
Message-ID: <13d64548b894fc1b351af2f9bbb861ce230144d0.1424173685.git.baruch@tkos.co.il> (raw)

External toolchain can also have been generated by Buildroot previously, as
the list that follows demonstrates. Add the word 'locally' at the right place
to make the point clearer.

Signed-off-by: Baruch Siach <baruch@tkos.co.il>
---
 toolchain/toolchain-external/toolchain-external.mk | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/toolchain/toolchain-external/toolchain-external.mk b/toolchain/toolchain-external/toolchain-external.mk
index 5a69eb88958e..4376c8ddbf1f 100644
--- a/toolchain/toolchain-external/toolchain-external.mk
+++ b/toolchain/toolchain-external/toolchain-external.mk
@@ -6,9 +6,9 @@
 
 #
 # This package implements the support for external toolchains, i.e
-# toolchains that have not been produced by Buildroot itself and that
-# Buildroot can download from the Web or that are already available on
-# the system on which Buildroot runs. So far, we have tested this
+# toolchains that have not been produced locally by Buildroot itself and
+# that Buildroot can download from the Web or that are already available
+# on the system on which Buildroot runs. So far, we have tested this
 # with:
 #
 #  * Toolchains generated by Crosstool-NG
-- 
2.1.4

             reply	other threads:[~2015-02-17 11:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-17 11:48 Baruch Siach [this message]
2015-02-19 20:36 ` [Buildroot] [PATCH] toolchain-external: clarify external toolchain description Thomas Petazzoni
2015-02-20  6:37   ` Baruch Siach
2015-02-20  8:02     ` 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=13d64548b894fc1b351af2f9bbb861ce230144d0.1424173685.git.baruch@tkos.co.il \
    --to=baruch@tkos.co.il \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.