From: "lukma at denx dot de" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/27601] New: License information update in localedata/locales/ast_ES
Date: Thu, 18 Mar 2021 10:12:02 +0000 [thread overview]
Message-ID: <bug-27601-716@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=27601
Bug ID: 27601
Summary: License information update in
localedata/locales/ast_ES
Product: glibc
Version: 2.34
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: localedata
Assignee: unassigned at sourceware dot org
Reporter: lukma at denx dot de
CC: libc-locales at sourceware dot org
Target Milestone: ---
Dear Community,
I've found some kind of mismatch in the localedata/locales/ast_ES file:
https://sourceware.org/git/?p=glibc.git;a=blob;f=localedata/locales/ast_ES;h=6d442bdc1a3bc88250e0a90f612b5a47b48b4763;hb=HEAD#l23
It looks like
% This file is under the
% GNU General Public License.
% Based in the an_ES Locale
clauses are not in sync with standardized "license" text in locale files
provided by SHA1: a4cea54b12ff33e81be4413abb74905020890330
Could somebody from FSF or responsible for licensing in GLIBC reply if those
aforementioned lines could be safely removed?
Thanks in advance,
Łukasz
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2021-03-18 10:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-18 10:12 lukma at denx dot de [this message]
2024-01-03 17:25 ` [Bug localedata/27601] " cvs-commit at gcc dot gnu.org
2024-01-03 17:27 ` maiku.fabian at gmail dot com
2024-01-03 17:27 ` maiku.fabian 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-27601-716@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=libc-locales@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).