From: alhe@linux.microsoft.com
To: docs@lists.yoctoproject.org
Cc: richard.purdie@linuxfoundation.org
Subject: [PATCH 0/3] Fix CROPS about link
Date: Sat, 28 Mar 2020 02:21:03 -0700 [thread overview]
Message-ID: <20200328092106.28231-1-alhe@linux.microsoft.com> (raw)
The CROPS link was outdated in several parts of the
documentation, there is not a lot to say about this
other than I updated it to the most reasonable link
I could find, and Scott seemed to use separate commits
for each different document, I'd be fine squashing
this into one commit but I tried keeping up with
what he was doing.
Alejandro Hernandez Samaniego (3):
dev-manual: Fix CROPS link
overview-manual-development-environment: Fix CROPS link
overview-manual-yp-intro: Fix CROPS link
documentation/dev-manual/dev-manual-start.xml | 4 ++--
.../overview-manual-development-environment.xml | 2 +-
documentation/overview-manual/overview-manual-yp-intro.xml | 4 ++--
3 files changed, 5 insertions(+), 5 deletions(-)
--
2.17.1
next 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 alhe [this message]
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 ` [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=20200328092106.28231-1-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox