<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/poky.git/documentation/overview-manual, branch kirkstone-4.0.18</title>
<subtitle>Mirror of git.yoctoproject.org/poky</subtitle>
<id>https://git.enea.com/cgit/linux/poky.git/atom?h=kirkstone-4.0.18</id>
<link rel='self' href='https://git.enea.com/cgit/linux/poky.git/atom?h=kirkstone-4.0.18'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/'/>
<updated>2024-04-19T11:50:39+00:00</updated>
<entry>
<title>manuals: fix trailing spaces</title>
<updated>2024-04-19T11:50:39+00:00</updated>
<author>
<name>Michael Opdenacker</name>
<email>michael.opdenacker@bootlin.com</email>
</author>
<published>2024-03-30T16:52:37+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=fac2a5eff5d149e7850b69bc2480292fa3a3f5e9'/>
<id>urn:sha1:fac2a5eff5d149e7850b69bc2480292fa3a3f5e9</id>
<content type='text'>
Fixing errors reported by "make sphinx-lint"

(From yocto-docs rev: 45b04c281a567e06fd2904166bcc26603e73e684)

Signed-off-by: Michael Opdenacker &lt;michael.opdenacker@bootlin.com&gt;
Signed-off-by: Steve Sakoman &lt;steve@sakoman.com&gt;
</content>
</entry>
<entry>
<title>manuals: replace hyphens with em dashes</title>
<updated>2024-03-25T14:11:26+00:00</updated>
<author>
<name>Michael Opdenacker</name>
<email>michael.opdenacker@bootlin.com</email>
</author>
<published>2022-03-29T06:46:15+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=5b75b5cbcf48845d4c4f740ac53ec50db20285db'/>
<id>urn:sha1:5b75b5cbcf48845d4c4f740ac53ec50db20285db</id>
<content type='text'>
Fix some hyphens being improperly used as em dashes.
See https://www.grammarly.com/blog/hyphens-and-dashes/

Using em dashes may also allow Sphinx to hyphenate
and break lines in the best way.

Note that the first character after an em dash not
supposed to be capitalized, unless a specific
rule applies, typically when what follows is a proper noun.

Fix a few misuses of parentheses in following text.

(From yocto-docs rev: a0d93ea1ddfdfbcde8dac3aa328307be778f9e3c)

Signed-off-by: Michael Opdenacker &lt;michael.opdenacker@bootlin.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
Signed-off-by: Steve Sakoman &lt;steve@sakoman.com&gt;
</content>
</entry>
<entry>
<title>ref-manual: variables: correct sdk installation default path</title>
<updated>2024-03-25T14:11:26+00:00</updated>
<author>
<name>Johan Bezem</name>
<email>jbezem.extern@arri.de</email>
</author>
<published>2024-02-26T16:15:06+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=48bd3888df136a4e9d8a97f942d8c4212f102cc0'/>
<id>urn:sha1:48bd3888df136a4e9d8a97f942d8c4212f102cc0</id>
<content type='text'>
The SDKPATH variable seems mistakenly identified as the
default path where the SDK will be installed by the generated
installation script, unless option '-d' or a manual input
overrides this default.

The intended variable is SDKPATHINSTALL. SDKPATH indicates
where the SDK is being composed and built.

The definitions have been added/updated.

(From yocto-docs rev: f7ce2abbdcff625356b337137e91f642ff6a4dc2)

Signed-off-by: Johan Bezem &lt;jbezem.extern@arri.de&gt;
Reviewed-by: Michael Opdenacker &lt;michael.opdenacker@bootlin.com&gt;
Signed-off-by: Steve Sakoman &lt;steve@sakoman.com&gt;
</content>
</entry>
<entry>
<title>manuals: updates for building on Windows (WSL 2)</title>
<updated>2024-03-01T15:19:55+00:00</updated>
<author>
<name>Michael Opdenacker</name>
<email>michael.opdenacker@bootlin.com</email>
</author>
<published>2022-10-14T11:50:51+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=54321fcec4a438978034d52fe98bc408f4dc0f0e'/>
<id>urn:sha1:54321fcec4a438978034d52fe98bc408f4dc0f0e</id>
<content type='text'>
- Use the Wikipedia naming scheme: WSL 2 instead of WSLv2
- Take into account Windows Server 2019 and 2022 which are
  supported too.
- Improve some explanations

(From yocto-docs rev: e64c1154c358128d76b1b8e3a5809dbaa8dc6881)

Signed-off-by: Michael Opdenacker &lt;michael.opdenacker@bootlin.com&gt;
Reviewed-by: Quentin Schulz &lt;foss@0leil.net&gt;
Signed-off-by: Steve Sakoman &lt;steve@sakoman.com&gt;
</content>
</entry>
<entry>
<title>manuals: suppress excess use of "following" word</title>
<updated>2024-03-01T15:19:54+00:00</updated>
<author>
<name>Michael Opdenacker</name>
<email>michael.opdenacker@bootlin.com</email>
</author>
<published>2024-02-09T16:48:06+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=fa870dfd0fd760ec1ab0342f5c82851c043f3eaf'/>
<id>urn:sha1:fa870dfd0fd760ec1ab0342f5c82851c043f3eaf</id>
<content type='text'>
To simplify the style, replace "Following is" and "Following are"
by "here is" and "here are", sounding more natural.

In some cases, also go further by simplifying "Here are/is xxx"
by "xxx are/is" when the "are" or "is" are not two far at
the end of the sentence.

In some cases too, completely remove the sentence, when
it's redundant with the preceding title.

(From yocto-docs rev: 2539f1b9cbf9bdd40eff93c6522dc76133debed7)

Signed-off-by: Michael Opdenacker &lt;michael.opdenacker@bootlin.com&gt;
CC: Daniel Ammann &lt;daniel.ammann@bytesatwork.ch&gt;
Signed-off-by: Steve Sakoman &lt;steve@sakoman.com&gt;
</content>
</entry>
<entry>
<title>manuals: document VSCode extension</title>
<updated>2024-01-24T14:04:56+00:00</updated>
<author>
<name>Enguerrand de Ribaucourt</name>
<email>enguerrand.de-ribaucourt@savoirfairelinux.com</email>
</author>
<published>2024-01-02T11:09:33+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=78e79d47c2e08a15b7833bc50ceb47f4854e8efe'/>
<id>urn:sha1:78e79d47c2e08a15b7833bc50ceb47f4854e8efe</id>
<content type='text'>
The VSCode extension is now officially maintained and published by the
Yocto Project so it should be referenced in the manuals to help users
discover it.

I located the most relevant places to reference the extension by looking
at how the old Eclipse plugin was documented in the 2.6 manuals as well
as the current Toaster references.

(From yocto-docs rev: 21ec0d3b52069dfc85ff47fb4f913a26a092c480)

Signed-off-by: Enguerrand de Ribaucourt &lt;enguerrand.de-ribaucourt@savoirfairelinux.com&gt;
Reviewed-by: Michael Opdenacker &lt;michael.opdenacker@bootlin.com&gt;
Signed-off-by: Steve Sakoman &lt;steve@sakoman.com&gt;
</content>
</entry>
<entry>
<title>manuals: update class references</title>
<updated>2023-11-28T15:00:32+00:00</updated>
<author>
<name>Michael Opdenacker</name>
<email>michael.opdenacker@bootlin.com</email>
</author>
<published>2023-11-14T16:44:01+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=a2d67684cc830181f00d4a432d10faf1c0495f25'/>
<id>urn:sha1:a2d67684cc830181f00d4a432d10faf1c0495f25</id>
<content type='text'>
Synchronizing with master whenever possible,
to make the branch easier to maintain.

(From yocto-docs rev: 825b1292ab08770b2d8cfdc1e11358a2790c1a1b)

Signed-off-by: Michael Opdenacker &lt;michael.opdenacker@bootlin.com&gt;
Signed-off-by: Steve Sakoman &lt;steve@sakoman.com&gt;
</content>
</entry>
<entry>
<title>overview-manual: concepts: Add Bitbake Tasks Map</title>
<updated>2023-11-28T15:00:32+00:00</updated>
<author>
<name>BELHADJ SALEM Talel</name>
<email>bhstalel@gmail.com</email>
</author>
<published>2023-11-01T08:40:20+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=6c9f29507f6e0b03a432ffde2bcc6439a7d1da99'/>
<id>urn:sha1:6c9f29507f6e0b03a432ffde2bcc6439a7d1da99</id>
<content type='text'>
Create a Map to detail how BitBake handles a recipe's tasks
and its compile/runtime dependencies along with detailed comments.

(From yocto-docs rev: 529c7bf6c434166f4d372166868d46f275eb5bea)

Signed-off-by: Talel BELHAJSALEM &lt;bhstalel@gmail.com&gt;
Reviewed-by: Michael Opdenacker &lt;michael.opdenacker@bootlin.com&gt;
Signed-off-by: Steve Sakoman &lt;steve@sakoman.com&gt;
</content>
</entry>
<entry>
<title>overview: Add note about non-reproducibility side effects</title>
<updated>2023-10-18T15:13:24+00:00</updated>
<author>
<name>Joshua Watt</name>
<email>JPEWhacker@gmail.com</email>
</author>
<published>2023-09-28T18:26:16+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=a721e0f85be99c686ac8c10a34a839fd593ddeae'/>
<id>urn:sha1:a721e0f85be99c686ac8c10a34a839fd593ddeae</id>
<content type='text'>
Adds an additional note about some of the side effects that can occur if
recipes are not reproducible and hash equivalence is enabled.

(From yocto-docs rev: aaf3e97c78e235bf3042c79ecdcf0b7c1a68ca8f)

Signed-off-by: Joshua Watt &lt;JPEWhacker@gmail.com&gt;
Reviewed-by: Michael Opdenacker &lt;michael.opdenacker@bootlin.com&gt;
Signed-off-by: Steve Sakoman &lt;steve@sakoman.com&gt;
</content>
</entry>
<entry>
<title>manuals: update former references to dev-manual/common-tasks</title>
<updated>2023-09-23T15:26:16+00:00</updated>
<author>
<name>Michael Opdenacker</name>
<email>michael.opdenacker@bootlin.com</email>
</author>
<published>2023-09-17T17:21:48+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=b099a1c252a8bd03bb882f6351f423b96648e921'/>
<id>urn:sha1:b099a1c252a8bd03bb882f6351f423b96648e921</id>
<content type='text'>
(From yocto-docs rev: f8bb4c392912f15bb78f6f25910f85897abb4e3d)

Signed-off-by: Michael Opdenacker &lt;michael.opdenacker@bootlin.com&gt;
Signed-off-by: Steve Sakoman &lt;steve@sakoman.com&gt;
</content>
</entry>
</feed>
