From: alhe@linux.microsoft.com
To: docs@lists.yoctoproject.org
Cc: richard.purdie@linuxfoundation.org
Subject: Re: [docs] [PATCH 1/3] dev-manual: Fix CROPS link
Date: Sat, 28 Mar 2020 15:16:31 -0600 [thread overview]
Message-ID: <976dd467-7da7-9219-cbc2-55096f57e162@linux.microsoft.com> (raw)
In-Reply-To: <3d99e73d-4ece-ab8b-f035-804759097951@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2262 bytes --]
Hey Armin,
On 3/28/20 12:53 PM, akuster wrote:
>
>
> On 3/28/20 2:21 AM, alhe@linux.microsoft.com wrote:
>> 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>
>> ---
>> documentation/dev-manual/dev-manual-start.xml | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/documentation/dev-manual/dev-manual-start.xml b/documentation/dev-manual/dev-manual-start.xml
>> index 59ffa49bb6..8d2f316f52 100644
>> --- a/documentation/dev-manual/dev-manual-start.xml
>> +++ b/documentation/dev-manual/dev-manual-start.xml
>> @@ -396,7 +396,7 @@
>> for development using the Yocto Project.
>> Your build host can be a native Linux machine (recommended) or it can
>> be a machine (Linux, Mac, or Windows) that uses
>> - <ulink url='https://git.yoctoproject.org/cgit/cgit.cgi/crops/about/'>CROPS</ulink>,
>> + <ulink url='https://github.com/crops/poky-container'>CROPS</ulink>,
>
> So what is "https://git.yoctoproject.org/git/crops"
> <https://git.yoctoproject.org/git/crops>
>
> used for then. If its wrong, we should either link it or remove that
> repo from YP git.
>
> - armin
As far as I could tell, its the same as https://github.com/crops/crops
which has been archived on github, and it says its deprecated, neither
of them have been updated in 4 years.
Alejandro
>> which leverages
>> <ulink url='https://www.docker.com/'>Docker Containers</ulink>.
>> <note>
>> @@ -517,7 +517,7 @@
>>
>> <para>
>> With
>> - <ulink url='https://github.com/crops/crops/blob/master/README.md'>CROPS</ulink>,
>> + <ulink url='https://github.com/crops/poky-container'>CROPS</ulink>,
>> which leverages
>> <ulink url='https://www.docker.com/'>Docker Containers</ulink>,
>> you can create a Yocto Project development environment that
>>
>
>
>
[-- Attachment #2: Type: text/html, Size: 4614 bytes --]
next prev parent reply other threads:[~2020-03-28 21:16 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 [this message]
2020-03-28 9:21 ` [PATCH 2/3] overview-manual-development-environment: " alhe
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=976dd467-7da7-9219-cbc2-55096f57e162@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox