public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/108413] copyrights for gcc 2023
Date: Mon, 16 Jan 2023 10:08:37 +0000	[thread overview]
Message-ID: <bug-108413-4-rdOTJogGhc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108413-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108413

--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #2)
> libstdc++-v3/src/c++17/fast_float/fast_float.h: unrecognised copyright
> holder: The fast_float authors

I think we need to add a special case for this. That is what it says in
https://github.com/fastfloat/fast_float/blob/main/LICENSE-MIT

> libstdc++-v3/include/c_compatibility/stdatomic.h: unrecognised copyright
> holder: The GCC developers

Oops, this one's wrong, I'll fix it.

  parent reply	other threads:[~2023-01-16 10:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-16  4:43 [Bug c++/108413] New: " unlvsur at live dot com
2023-01-16  4:52 ` [Bug libstdc++/108413] " pinskia at gcc dot gnu.org
2023-01-16  9:28 ` jakub at gcc dot gnu.org
2023-01-16 10:04 ` [Bug other/108413] " cvs-commit at gcc dot gnu.org
2023-01-16 10:08 ` redi at gcc dot gnu.org [this message]
2023-01-16 10:23 ` cvs-commit at gcc dot gnu.org
2023-01-16 10:32 ` cvs-commit at gcc dot gnu.org
2023-01-16 10:40 ` cvs-commit at gcc dot gnu.org
2023-01-16 10:59 ` jakub at gcc dot gnu.org
2023-01-17 15:52 ` gaius at gcc dot gnu.org
2023-03-28 23:33 ` cvs-commit at gcc dot gnu.org

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-108413-4-rdOTJogGhc@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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).