From: "Leif Lindholm" <quic_llindhol@quicinc.com>
To: <devel@edk2.groups.io>, <rebecca@os.amperecomputing.com>
Cc: Nhi Pham <nhi@os.amperecomputing.com>, <patches@amperecomputing.com>
Subject: Re: [edk2-devel] [PATCH edk2-platforms 1/1] Platform/Ampere: Update Readme.md
Date: Tue, 12 Sep 2023 16:11:51 +0100 [thread overview]
Message-ID: <15f36b03-317f-4ed2-a35c-605d7234d2f9@quicinc.com> (raw)
In-Reply-To: <4e1af826-cccf-4138-8b3e-1c0bd7462452@os.amperecomputing.com>
On 2023-09-12 14:07, Rebecca Cran via groups.io wrote:
> On 9/12/2023 3:58 AM, Leif Lindholm via groups.io wrote:
>
>> So, it's really good that you add "known good" versions so that if
>> someone runs into a problem around toolchain version compatibility,
>> they know what to use. But anything in edk2-platform should be kept up
>> to date so that it builds on current operating systems.
>
> Really, I think we'd want to remove everything from the Readme.md except
> perhaps the "Additional build tools" section.
I would be OK with that too.
/
Leif
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#108544): https://edk2.groups.io/g/devel/message/108544
Mute This Topic: https://groups.io/mt/101298216/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/leave/12367111/7686176/1913456212/xyzzy [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
prev parent reply other threads:[~2023-09-12 15:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-11 17:44 [edk2-devel] [PATCH edk2-platforms 1/1] Platform/Ampere: Update Readme.md Rebecca Cran via groups.io
2023-09-12 1:54 ` Nhi Pham via groups.io
2023-09-12 9:58 ` Leif Lindholm
2023-09-12 13:07 ` Rebecca Cran via groups.io
2023-09-12 15:11 ` Leif Lindholm [this message]
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-list 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=15f36b03-317f-4ed2-a35c-605d7234d2f9@quicinc.com \
--to=devel@edk2.groups.io \
/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