From: "Michael Opdenacker" <michael.opdenacker@bootlin.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: YP docs mailing list <docs@lists.yoctoproject.org>
Subject: [master-next] Pull request
Date: Tue, 6 Apr 2021 22:56:04 +0200 [thread overview]
Message-ID: <03e26f4b-2dfe-33a2-3eea-607a0f088cc0@bootlin.com> (raw)
Hi Richard,
The following changes since commit 5036fea7854c3152a0c148d8ab1668e01b38697d:
poky.yaml: change gcc-multilib to gcc (2021-04-06 15:07:42 +0100)
are available in the Git repository at:
git://git.yoctoproject.org/yocto-docs master-next
http://git.yoctoproject.org/cgit/cgit.cgi/yocto-docs/log/?h=master-next
for you to fetch changes up to 67d5fb17f31292abb1e2dec7e436a7d8a534e63d:
manuals: fix suspicious newlines (2021-04-06 22:18:03 +0200)
----------------------------------------------------------------
Janne Kiiskila (1):
UBUNTU sudo apt git instead of git-core
Michael Opdenacker (7):
Spellcheck and capitalization fixes
SDK manual: fix reference to appendix
Quick build: checkout a branch instead of a fixed tag
Fix typos and spacing
overview-manual: style improvements
ref-manual: fix typo
manuals: fix suspicious newlines
documentation/README | 2 +-
documentation/boilerplate.rst | 2 +-
documentation/brief-yoctoprojectqs/index.rst | 65
++++++++++++++++++++++++++++++++++++++++-------------------------
documentation/bsp-guide/bsp.rst | 6 +++---
documentation/dev-manual/common-tasks.rst | 33
++++++++++++++-------------------
documentation/kernel-dev/common.rst | 2 +-
documentation/kernel-dev/maint-appx.rst | 2 +-
documentation/overview-manual/concepts.rst | 3 +--
documentation/overview-manual/yp-intro.rst | 88
+++++++++++++++++++++++++++++++++++++++++++---------------------------------------------
documentation/poky.yaml | 2 +-
documentation/profile-manual/usage.rst | 30
+++++++++++++++---------------
documentation/ref-manual/TODO | 6 +++---
documentation/ref-manual/classes.rst | 2 +-
documentation/ref-manual/faq.rst | 2 +-
documentation/ref-manual/kickstart.rst | 4 ++--
documentation/ref-manual/migration-1.7.rst | 2 +-
documentation/ref-manual/migration-2.1.rst | 2 +-
documentation/ref-manual/migration-3.2.rst | 2 +-
documentation/ref-manual/release-process.rst | 2 +-
documentation/ref-manual/resources.rst | 4 ++--
documentation/ref-manual/structure.rst | 2 +-
documentation/ref-manual/system-requirements.rst | 4 ++--
documentation/ref-manual/variables.rst | 18
++++++++----------
documentation/sdk-manual/appendix-customizing.rst | 2 +-
documentation/sdk-manual/extensible.rst | 8 +++-----
documentation/sdk-manual/working-projects.rst | 9 ++-------
documentation/test-manual/intro.rst | 10 +++++-----
documentation/test-manual/test-process.rst | 4 ++--
documentation/test-manual/understand-autobuilder.rst | 16 ++++++++--------
documentation/toaster-manual/reference.rst | 2 +-
documentation/toaster-manual/setup-and-use.rst | 8 ++++----
31 files changed, 171 insertions(+), 173 deletions(-)
--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next reply other threads:[~2021-04-06 20:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-06 20:56 Michael Opdenacker [this message]
2021-04-06 21:36 ` [master-next] Pull request Richard Purdie
2021-04-07 11:54 ` [docs] " Michael Opdenacker
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=03e26f4b-2dfe-33a2-3eea-607a0f088cc0@bootlin.com \
--to=michael.opdenacker@bootlin.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.