From: alhe@linux.microsoft.com
To: docs@lists.yoctoproject.org
Cc: richard.purdie@linuxfoundation.org
Subject: [PATCH 2/3] overview-manual-development-environment: Fix CROPS link
Date: Sat, 28 Mar 2020 02:21:05 -0700 [thread overview]
Message-ID: <20200328092106.28231-3-alhe@linux.microsoft.com> (raw)
In-Reply-To: <20200328092106.28231-1-alhe@linux.microsoft.com>
The link used in the documentation points to a file
that no longer exists on the crops repository.
Use the poky-container repo instead since it is more
accurate and updated.
Signed-off-by: Alejandro Hernandez Samaniego <alejandro@enedino.org>
Signed-off-by: Alejandro Hernandez Samaniego <alhe@linux.microsoft.com>
---
.../overview-manual/overview-manual-development-environment.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/documentation/overview-manual/overview-manual-development-environment.xml b/documentation/overview-manual/overview-manual-development-environment.xml
index 2f1bd1610d..36ebf8a321 100644
--- a/documentation/overview-manual/overview-manual-development-environment.xml
+++ b/documentation/overview-manual/overview-manual-development-environment.xml
@@ -87,7 +87,7 @@
as its operating system as your development host.
When you have a Mac or Windows-based system, you can set it up
as the development host by using
- <ulink url='https://git.yoctoproject.org/cgit/cgit.cgi/crops/about/'>CROPS</ulink>,
+ <ulink url='https://github.com/crops/poky-container'>CROPS</ulink>,
which leverages
<ulink url='https://www.docker.com/'>Docker Containers</ulink>.
Once you take the steps to set up a CROPS machine, you effectively
--
2.17.1
next prev parent reply other threads:[~2020-03-28 9:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-28 9:21 [PATCH 0/3] Fix CROPS about link alhe
2020-03-28 9:21 ` [PATCH 1/3] dev-manual: Fix CROPS link alhe
2020-03-28 18:53 ` [docs] " akuster
2020-03-28 21:16 ` alhe
2020-03-28 9:21 ` alhe [this message]
2020-03-28 9:21 ` [PATCH 3/3] overview-manual-yp-intro: " alhe
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=20200328092106.28231-3-alhe@linux.microsoft.com \
--to=alhe@linux.microsoft.com \
--cc=docs@lists.yoctoproject.org \
--cc=richard.purdie@linuxfoundation.org \
/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.