mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Roland Hieber <r.hieber@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Roland Hieber <r.hieber@pengutronix.de>
Subject: [ptxdist] [PATCH v2] doc: environment: update link to toolchain download
Date: Mon,  5 Feb 2018 02:30:16 +0100	[thread overview]
Message-ID: <20180205013016.3712-1-r.hieber@pengutronix.de> (raw)
In-Reply-To: <20171205221854.31379-1-r.hieber@pengutronix.de>

Signed-off-by: Roland Hieber <r.hieber@pengutronix.de>
---
v2: Now that respective page has been written :-)
---

 doc/environment.rst | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/doc/environment.rst b/doc/environment.rst
index 9cad2f300..2624a76a0 100644
--- a/doc/environment.rst
+++ b/doc/environment.rst
@@ -60,9 +60,9 @@ Package Descriptions:
 Toolchains:
     PTXdist does not come with a pre-built binary toolchain.
     Nevertheless, PTXdist itself is able to build toolchains, which are
-    provided by the OSELAS.Toolchain() project. More in-deep information
-    about the OSELAS.Toolchain() project can be found here:
-    http://www.pengutronix.de/oselas/toolchain/index_en.html
+    provided by the OSELAS.Toolchain() project.
+    The different OSELAS toolchains can be found at
+    https://www.pengutronix.de/en/software/toolchain.html.
 
     Building a toolchain is not part of this manual, refer for
     application note “Building Toolchains” instead.
-- 
2.15.1


_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

      parent reply	other threads:[~2018-02-05  1:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-05 22:18 [ptxdist] [PATCH] doc: " Roland Hieber
2017-12-06  7:17 ` Alexander Dahl
2017-12-06  8:50   ` Juergen Borleis
2018-02-05  1:30 ` Roland Hieber [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=20180205013016.3712-1-r.hieber@pengutronix.de \
    --to=r.hieber@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    /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