From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 471BF3853804; Mon, 30 May 2022 15:25:54 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 471BF3853804 From: "fweimer at redhat dot com" To: glibc-bugs@sourceware.org Subject: [Bug libc/28007] Add SPDX license identifiers Date: Mon, 30 May 2022 15:25:54 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: libc X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: fweimer at redhat dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: security- X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: glibc-bugs@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Glibc-bugs mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 May 2022 15:25:54 -0000 https://sourceware.org/bugzilla/show_bug.cgi?id=3D28007 --- Comment #10 from Florian Weimer --- (In reply to David Edelsohn from comment #7) > Many security tools now are looking for SPDX license identifiers and the > lack of the clear information in SPDX license identifier format is a grow= ing > inhibitor to GLIBC. I'm worried that adding those identifiers gives an implied promise about th= eir correctness. There is also the impediment to future development because we have to discu= ss whether we need to copy SPDX identifiers as well when copying code around, = and if a file has multiple such identifiers, if all should be copied, or just t= hose pertaining to the code being copied. --=20 You are receiving this mail because: You are on the CC list for the bug.=