public inbox for docs@lists.yoctoproject.org
 help / color / mirror / Atom feed
From: Michael Opdenacker <michael.opdenacker@bootlin.com>
To: quentin.schulz@theobroma-systems.com
Cc: docs@lists.yoctoproject.org
Subject: Re: [docs] [PATCH] ref-manual: update references to release notes
Date: Fri, 9 Dec 2022 16:22:12 +0100	[thread overview]
Message-ID: <f1540530-9eeb-fa58-a60c-93e1ef8e8d40@bootlin.com> (raw)
In-Reply-To: <0238be8d-2341-45d5-dd5d-ebfd1ea1ccf1@theobroma-systems.com>

Hi Quentin,

Thanks for the review.

Am 09.12.22 um 11:05 schrieb Quentin Schulz via lists.yoctoproject.org:
> Hi Michael,
>
> On 12/8/22 16:16, Michael Opdenacker via lists.yoctoproject.org wrote:
>>
>> +         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.

-- 
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com



  reply	other threads:[~2022-12-09 15:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-08 15:16 [PATCH] ref-manual: update references to release notes michael.opdenacker
2022-12-09 10:05 ` [docs] " Quentin Schulz
2022-12-09 15:22   ` Michael Opdenacker [this message]
2022-12-09 16:38     ` Quentin Schulz
2022-12-09 18:24       ` 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=f1540530-9eeb-fa58-a60c-93e1ef8e8d40@bootlin.com \
    --to=michael.opdenacker@bootlin.com \
    --cc=docs@lists.yoctoproject.org \
    --cc=quentin.schulz@theobroma-systems.com \
    /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