ref-manual: update references to release notes
PATCH 1/1 ref-manual: update references to release notes
From: Michael Opdenacker <[email protected]>
Now part of the Yocto Project manual.
--- documentation/ref-manual/resources.rst | 8 +++----- documentation/ref-manual/variables.rst | 10 ++++------ 2 files changed, 7 insertions(+), 11 deletions(-)
documentation/ref-manual/resources.rst +3 -5
@@ -171,11 +171,9 @@ Here is a list of resources you might find helpful: - :yocto_wiki:`FAQ </FAQ>`: A list of commonly asked questions and their answers. -- Release Notes: Features, updates and known issues for the current - release of the Yocto Project. To access the Release Notes, go to the - :yocto_home:`Downloads </software-overview/downloads>` page on - the Yocto Project website and click on the "RELEASE INFORMATION" link - for the appropriate release. +- :yocto_docs:`Release Information </migration-guides/>`: + Migration guides, release notes, new features, updates and known issues + for the current and past releases of the Yocto Project. - :yocto_bugs:`Bugzilla <>`: The bug tracking application the Yocto Project uses. If you find problems with the Yocto Project,
documentation/ref-manual/variables.rst +4 -6
@@ -8465,12 +8465,10 @@ system and gives an overview of their function and contents. If :term:`TCMODE` is set to a value other than "default", then it is your responsibility to ensure that the toolchain is compatible with the default toolchain. Using older or newer versions of these - components might cause build problems. See the Release Notes for - the Yocto Project release for the specific components with which - the toolchain must be compatible. To access the Release Notes, go - to the :yocto_home:`Downloads </software-overview/downloads>` - page on the Yocto Project website and click on the "RELEASE - INFORMATION" link for the appropriate release. + components might cause build problems. See + :yocto_docs:`Release Information </migration-guides/>` for your + version of the Yocto Project, to find the specific components with + which the toolchain must be compatible. The :term:`TCMODE` variable is similar to :term:`TCLIBC`, which controls the variant of the GNU standard C library (``libc``)
Signature · 1 line
2.37.2
Hi Michael,
Quoted 38 lines · Michael Opdenacker via lists.yoctoproject.org
From: Michael Opdenacker <[email protected]>
Now part of the Yocto Project manual.
Signed-off-by Michael Opdenacker <[email protected]>--- documentation/ref-manual/resources.rst | 8 +++----- documentation/ref-manual/variables.rst | 10 ++++------ 2 files changed, 7 insertions(+), 11 deletions(-)documentation/ref-manual/resources.rst +3
-5@@ -171,11 +171,9 @@ Here is a list of resources you might find helpful: - :yocto_wiki:`FAQ </FAQ>`: A list of commonly asked questions and their answers. -- Release Notes: Features, updates and known issues for the current - release of the Yocto Project. To access the Release Notes, go to the - :yocto_home:`Downloads </software-overview/downloads>` page on - the Yocto Project website and click on the "RELEASE INFORMATION" link - for the appropriate release. +- :yocto_docs:`Release Information </migration-guides/>`: + Migration guides, release notes, new features, updates and known issues + for the current and past releases of the Yocto Project. - :yocto_bugs:`Bugzilla <>`: The bug tracking application the Yocto Project uses. If you find problems with the Yocto Project,documentation/ref-manual/variables.rst +0
-1@@ -8465,12 +8465,10 @@ system and gives an overview of their function and contents. If :term:`TCMODE` is set to a value other than "default", then it is your responsibility to ensure that the toolchain is compatible with the default toolchain. Using older or newer versions of these - components might cause build problems. See the Release Notes for
documentation/ref-manual/variables.rst system and gives an overview of their function and contents. · line 8472
Quoted 10 lines
documentation/ref-manual/variables.rst +4
-5- the Yocto Project release for the specific components with which - the toolchain must be compatible. To access the Release Notes, go - to the :yocto_home:`Downloads </software-overview/downloads>` - page on the Yocto Project website and click on the "RELEASE - INFORMATION" link for the appropriate release. + components might cause build problems. See + :yocto_docs:`Release Information </migration-guides/>` for your + version of the Yocto Project, to find the specific components with + which the toolchain must be compatible.
Where is this info located exactly?
Cheers,
Quentin
Hi Quentin,
Thanks for the review.
Am 09.12.22 um 11:05 schrieb Quentin Schulz via lists.yoctoproject.org:
Quoted 4 lines
Hi Michael,
Quoted 1 line · Michael Opdenacker via lists.yoctoproject.org
Quoted 8 lines
Quoted 6 lines
+ components might cause build problems. See
+ :yocto_docs:Release Information </migration-guides/>for your
+ version of the Yocto Project, to find the specific components with
+ which the toolchain must be compatible.Where is this info located exactly?
Well, information is scarce. In the release notes, you have at least the glibc version which is supported, and sometimes but not systematically the supported gcc and binutils versions.
Shall I say "where you may find the specific components..."? Cheers
Michael.
Signature · 3 lines
Michael Opdenacker, Bootlin Embedded Linux and Kernel engineering https://bootlin.com
Hi Michael,
Quoted 16 lines · Michael Opdenacker
Hi Quentin,
Thanks for the review.
Am 09.12.22 um 11:05 schrieb Quentin Schulz via lists.yoctoproject.org:
Quoted 11 lines
Hi Michael,
Quoted 7 lines · Michael Opdenacker via lists.yoctoproject.org
+ components might cause build problems. See
+ :yocto_docs:Release Information </migration-guides/>for your
+ version of the Yocto Project, to find the specific components with
+ which the toolchain must be compatible.
Quoted 5 lines
Quoted 1 line
Where is this info located exactly?
Well, information is scarce. In the release notes, you have at least the glibc version which is supported, and sometimes but not systematically the supported gcc and binutils versions.
Shall I say "where you may find the specific components..."?
I'm just wondering how this would help people if there's no actual way of knowing the specific components or their version.
In the end, if there's not more information than the previous location, I guess the patch in itself is fine and another patch/workflow/process can be put in place to make this more helpful (if even possible).
Cheers,
Quentin
Am 09.12.22 um 17:38 schrieb Quentin Schulz via lists.yoctoproject.org:
Quoted 21 lines
Hi Michael,
Quoted 18 lines · Michael Opdenacker
Hi Quentin,
Thanks for the review.
Am 09.12.22 um 11:05 schrieb Quentin Schulz via lists.yoctoproject.org:
Quoted 12 lines
Hi Michael,
Quoted 7 lines · Michael Opdenacker via lists.yoctoproject.org
+ components might cause build problems. See
+ :yocto_docs:Release Information </migration-guides/>for your
+ version of the Yocto Project, to find the specific components with
+ which the toolchain must be compatible.Where is this info located exactly?
Quoted 7 lines
Quoted 3 lines
Well, information is scarce. In the release notes, you have at least the glibc version which is supported, and sometimes but not systematically the supported gcc and binutils versions.
Shall I say "where you may find the specific components..."?
I'm just wondering how this would help people if there's no actual way of knowing the specific components or their version.
In the end, if there's not more information than the previous location, I guess the patch in itself is fine and another patch/workflow/process can be put in place to make this more helpful (if even possible).
Agreed. We can improve this in a future commit.
Cheers
Michael.
Signature · 3 lines
Michael Opdenacker, Bootlin Embedded Linux and Kernel engineering https://bootlin.com