public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dje at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/28007] New: Add SPDX license identifiers
Date: Tue, 22 Jun 2021 17:42:13 +0000 [thread overview]
Message-ID: <bug-28007-131@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=28007
Bug ID: 28007
Summary: Add SPDX license identifiers
Product: glibc
Version: unspecified
Status: NEW
Severity: enhancement
Priority: P2
Component: libc
Assignee: unassigned at sourceware dot org
Reporter: dje at sourceware dot org
CC: codonell at redhat dot com, drepper.fsp at gmail dot com
Target Milestone: ---
Add appropriate SPDX license identifiers to GNU libc source code files.
https://spdx.org/licenses/
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2021-06-22 17:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-22 17:42 dje at sourceware dot org [this message]
2021-06-25 11:53 ` [Bug libc/28007] " carlos at redhat dot com
2022-05-25 19:12 ` Martin.Jansa at gmail dot com
2022-05-25 20:20 ` carlos at redhat dot com
2022-05-28 12:29 ` richard.purdie at linuxfoundation dot org
2022-05-30 14:21 ` carlos at redhat dot com
2022-05-30 15:04 ` fweimer at redhat dot com
2022-05-30 15:12 ` dje at sourceware dot org
2022-05-30 15:22 ` richard.purdie at linuxfoundation dot org
2022-05-30 15:25 ` richard.purdie at linuxfoundation dot org
2022-05-30 15:25 ` fweimer at redhat dot com
2022-05-30 15:32 ` fweimer at redhat dot com
2022-05-30 16:24 ` richard.purdie at linuxfoundation dot org
2022-05-30 17:12 ` carlos at redhat dot com
2022-05-30 17:21 ` carlos at redhat dot com
2022-05-31 15:49 ` rwmacleod at gmail dot com
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=bug-28007-131@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@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).