public inbox for
help / color / mirror / Atom feed
From: Sebastian Huber <>
Subject: [newlib-cygwin] sys: further adoption of SPDX licensing ID tags.
Date: Mon, 11 Jul 2022 11:50:08 +0000 (GMT)	[thread overview]
Message-ID: <> (raw);h=eb4cbf4fd3e4ebcc2db02c488fa0ef88858ab973

commit eb4cbf4fd3e4ebcc2db02c488fa0ef88858ab973
Author: Pedro F. Giffuni <>
Date:   Mon Nov 20 19:43:44 2017 +0000

    sys: further adoption of SPDX licensing ID tags.
    Mainly focus on files that use BSD 3-Clause license.
    The Software Package Data Exchange (SPDX) group provides a specification
    to make it easier for automated tools to detect and summarize well known
    opensource licenses. We are gradually adopting the specification, noting
    that the tags are considered only advisory and do not, in any way,
    superceed or replace the license texts.
    Special thanks to Wind River for providing access to "The Duke of
    Highlander" tool: an older (2014) run over FreeBSD tree was useful as a
    starting point.

 newlib/libc/sys/rtems/include/sys/param.h | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/newlib/libc/sys/rtems/include/sys/param.h b/newlib/libc/sys/rtems/include/sys/param.h
index 8ed9269d0..925f0fc44 100644
--- a/newlib/libc/sys/rtems/include/sys/param.h
+++ b/newlib/libc/sys/rtems/include/sys/param.h
@@ -1,4 +1,6 @@
+ * SPDX-License-Identifier: BSD-3-Clause
+ *
  * Copyright (c) 1982, 1986, 1989, 1993
  *	The Regents of the University of California.  All rights reserved.
  * (c) UNIX System Laboratories, Inc.

             reply	other threads:[~2022-07-11 11:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-11 11:50 Sebastian Huber [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-12-04  9:03 Sebastian Huber
2018-08-24 13:10 Sebastian Huber
2018-07-30  8:52 Sebastian Huber

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).