From: "Victor L. Do Nascimento" <victor.donascimento@arm.com>
To: <newlib@sourceware.org>
Cc: <Richard.Earnshaw@foss.arm.com>
Subject: [PATCH] COPYING.NEWLIB: Arm licence entry amendment
Date: Thu, 19 Jan 2023 17:17:39 +0000 [thread overview]
Message-ID: <yw8jbkmua1fw.fsf@arm.com> (raw)
Add relevant SPDX-License-Identifier to Arm licence entry in
COPYING.NEWLIB.
---
COPYING.NEWLIB | 2 ++
1 file changed, 2 insertions(+)
diff --git a/COPYING.NEWLIB b/COPYING.NEWLIB
index d54ed293d..ee14bb349 100644
--- a/COPYING.NEWLIB
+++ b/COPYING.NEWLIB
@@ -762,6 +762,8 @@ SUCH DAMAGE.
(35) - Arm Ltd
+ SPDX-License-Identifier: BSD-3-Clause
+
Copyright (c) 2009-2022 Arm Ltd
All rights reserved.
--
2.36.1
next reply other threads:[~2023-01-19 17:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 17:17 Victor L. Do Nascimento [this message]
2023-01-19 20:06 ` Jeff Johnston
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=yw8jbkmua1fw.fsf@arm.com \
--to=victor.donascimento@arm.com \
--cc=Richard.Earnshaw@foss.arm.com \
--cc=newlib@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).