<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/poky.git/README, branch master</title>
<subtitle>Mirror of git.yoctoproject.org/poky</subtitle>
<id>https://git.enea.com/cgit/linux/poky.git/atom?h=master</id>
<link rel='self' href='https://git.enea.com/cgit/linux/poky.git/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/'/>
<updated>2026-02-03T10:04:25+00:00</updated>
<entry>
<title>README: switch to released documentation URLs</title>
<updated>2026-02-03T10:04:25+00:00</updated>
<author>
<name>Antonin Godard</name>
<email>antonin.godard@bootlin.com</email>
</author>
<published>2026-01-20T13:17:51+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=5c2b3d184065b0a15695bad7db455ef65653e4c6'/>
<id>urn:sha1:5c2b3d184065b0a15695bad7db455ef65653e4c6</id>
<content type='text'>
Update the documentation links to their released form, as those now
contain the bitbake-setup and poky-manual-setup instructions (since
Whinlatter).

Also: long live Poky!

Signed-off-by: Antonin Godard &lt;antonin.godard@bootlin.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>README: Fix typo</title>
<updated>2025-11-11T11:28:00+00:00</updated>
<author>
<name>Osama Abdelkader</name>
<email>osama.abdelkader@gmail.com</email>
</author>
<published>2025-11-08T19:58:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=485d9c126adad5764cca8d27fb437be7855b484a'/>
<id>urn:sha1:485d9c126adad5764cca8d27fb437be7855b484a</id>
<content type='text'>
ut meant -&gt; it meant

Signed-off-by: Osama Abdelkader &lt;osama.abdelkader@gmail.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>The poky repository master branch is no longer being updated.</title>
<updated>2025-11-07T17:43:38+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2025-11-07T17:43:38+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=7b5fa59751262b9f47fa44db0374662d0fa3fa67'/>
<id>urn:sha1:7b5fa59751262b9f47fa44db0374662d0fa3fa67</id>
<content type='text'>
You can either:

a) switch to individual clones of bitbake, openembedded-core, meta-yocto and yocto-docs

   https://docs.yoctoproject.org/dev/dev-manual/poky-manual-setup.html

b) use the new bitbake-setup

   https://docs.yoctoproject.org/bitbake/dev/bitbake-user-manual/bitbake-user-manual-environment-setup.html

You can find more information in our documentation: https://docs.yoctoproject.org/

Note that "poky" the distro setting is still available in meta-yocto as
before and we continue to use and maintain that.

Long live Poky!

Some further information on the background of this change can be found
in: https://lists.openembedded.org/g/openembedded-architecture/message/2179

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>The poky repository master branch is no longer being updated.</title>
<updated>2025-11-07T16:36:50+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2025-11-07T16:36:30+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=453df63af0c857c24804271da7f55691d0ed27f8'/>
<id>urn:sha1:453df63af0c857c24804271da7f55691d0ed27f8</id>
<content type='text'>
You can either:

a) switch to individual clones of bitbake, openembedded-core, meta-yocto and yocto-docs

   https://docs.yoctoproject.org/dev/dev-manual/poky-manual-setup.html

b) use the new bitbake-setup

   https://docs.yoctoproject.org/dev/dev-manual/poky-manual-setup.html

You can find more information in our documentation: https://docs.yoctoproject.org/

Note that "poky" the distro setting is still available in meta-yocto as
before and we continue to use and maintain that.

Long live Poky!

Some further information on the background of this change can be found
in: https://lists.openembedded.org/g/openembedded-architecture/message/2179

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>The poky repository master branch is no longer being updated.</title>
<updated>2025-11-07T13:31:53+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2025-11-07T13:31:53+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=8c22ff0d8b70d9b12f0487ef696a7e915b9e3173'/>
<id>urn:sha1:8c22ff0d8b70d9b12f0487ef696a7e915b9e3173</id>
<content type='text'>
You can either:

a) switch to individual clones of bitbake, openembedded-core, meta-yocto and yocto-docs

b) use the new bitbake-setup

You can find information about either approach in our documentation:
https://docs.yoctoproject.org/

Note that "poky" the distro setting is still available in meta-yocto as
before and we continue to use and maintain that.

Long live Poky!

Some further information on the background of this change can be found
in: https://lists.openembedded.org/g/openembedded-architecture/message/2179

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>meta-yocto: Restructure and tidy up READMEs</title>
<updated>2017-09-14T12:36:22+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2017-09-14T11:00:35+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=abea8ec5063998e0e2b822be7704c0d14569df0e'/>
<id>urn:sha1:abea8ec5063998e0e2b822be7704c0d14569df0e</id>
<content type='text'>
The YP Compat v2 standard requres a more specific README structure. Bring
meta-yocto to the required standard and clean up some of the data in the
READMEs whilst in there.

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>meta-yocto: Rename to meta-poky to better match its purpose</title>
<updated>2016-02-28T11:31:17+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2016-02-16T16:42:58+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=9d5483c37523ff3d334c98cafb848282b54962cd'/>
<id>urn:sha1:9d5483c37523ff3d334c98cafb848282b54962cd</id>
<content type='text'>
"poky" is the reference distribution for the Yocto Project. This renames
the layer within the meta-yocto repository to meta-poky, better matching
what that layer contains.

A layer.conf file is left behind as this is the only way which allows
existing builds to migrate safely to the new name. It will be removed
at some future point.

This change requires the corresponding OE-Core change to handle the
migration and the changes to the infrastructure to support this.

(From meta-yocto rev: d0c88df2e14672fca4ebbde93c5efbcd0e4fa9b6)

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>README: expand the Where To Send Patches section</title>
<updated>2015-03-04T17:07:37+00:00</updated>
<author>
<name>Ross Burton</name>
<email>ross.burton@intel.com</email>
</author>
<published>2015-03-04T13:01:53+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=bef8558f0e1a73107743417d8b2b772744ed9c28'/>
<id>urn:sha1:bef8558f0e1a73107743417d8b2b772744ed9c28</id>
<content type='text'>
(From meta-yocto rev: 20903fc4df6eed27202c2bf015d2da402191205a)

Signed-off-by: Ross Burton &lt;ross.burton@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>README: fix DISTRO = "" reference</title>
<updated>2014-01-02T12:58:54+00:00</updated>
<author>
<name>Paul Eggleton</name>
<email>paul.eggleton@linux.intel.com</email>
</author>
<published>2013-12-23T20:59:50+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=b8a3fb2f638c63d357a2fd326308350cacbf503a'/>
<id>urn:sha1:b8a3fb2f638c63d357a2fd326308350cacbf503a</id>
<content type='text'>
DISTRO should be set to "nodistro" for distro-less configurations since
empty string results in empty items ending up in OVERRIDES leading to
unexpected behaviour with FILESPATH.

(From OE-Core rev: 25436b6813b6245faeb981cf93a0c32b871dd8d3)

Signed-off-by: Paul Eggleton &lt;paul.eggleton@linux.intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>README: Clarify where to send patches</title>
<updated>2012-08-22T13:05:00+00:00</updated>
<author>
<name>Darren Hart</name>
<email>dvhart@linux.intel.com</email>
</author>
<published>2012-08-21T16:27:16+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=d15f1265015f47e122ca3eed713037b36f600a42'/>
<id>urn:sha1:d15f1265015f47e122ca3eed713037b36f600a42</id>
<content type='text'>
There is still a great deal of confusion over where patches for the
various components of the poky repository should be sent. Attempt to
mitigate this by including a blurb in the poky README similar to what
other layers and repositories do.

V2: Call out the special care required when dealing with the scripts
    directory per Saul Wold's recommendation.

V3: Recommend applying patches to oe-core prior to sending patches to
    the oe-core mailing list.

(From meta-yocto rev: d2747240e75ca0d43f569161694799c3d5d23014)

Signed-off-by: Darren Hart &lt;dvhart@linux.intel.com&gt;
CC: Richard Purdie &lt;richard.purdie@intel.com&gt;
CC: Paul Gortmaker &lt;paul.gortmaker@windriver.com&gt;
CC: Paul Eggleton &lt;paul.eggleton@linux.intel.com&gt;
CC: Khem Raj &lt;raj.khem@gmail.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
</feed>
