public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit 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:04:22 +0000	[thread overview]
Message-ID: <bug-108413-4-7Wl9EmpR0Q@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 #3 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:

https://gcc.gnu.org/g:d1c6a352cad473edbacecad5ceb49eaaa4e67a52

commit r13-5187-gd1c6a352cad473edbacecad5ceb49eaaa4e67a52
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Mon Jan 16 11:03:30 2023 +0100

    contrib: Partial fix for failed update-copyright --this year [PR108413]

    As mentioned on IRC or in PR108413, the last update-copyright.py --this
year
    failed and that is why we are in a strange state where some copyrights have
    been updated and others have not.
    The full list of errors I got was I think:
    gcc/m2/mc-boot/GmcOptions.c: unrecognised copyright: comment (f, (const
char *) "Copyright (C) ''2021'' Free Software Foundation, Inc.", 53);
    gcc/m2/mc-boot/GmcOptions.c: unrecognised copyright: comment (f, (const
char *) "Copyright (C) ''2021'' Free Software Foundation, Inc.", 53);
    gcc/testsuite/gm2/switches/pedantic-params/pass/Strings.mod: unrecognised
copyright holder: Faculty of Information Technology,
    gcc/testsuite/gm2/switches/pedantic-params/pass/Strings2.mod: unrecognised
copyright holder: Faculty of Information Technology,
    libphobos/libdruntime/__builtins.di: unrecognised copyright: * Copyright:
Copyright Digital Mars 2022
    libstdc++-v3/src/c++17/fast_float/fast_float.h: unrecognised copyright
holder: The fast_float authors
    libstdc++-v3/include/c_compatibility/stdatomic.h: unrecognised copyright
holder: The GCC developers

    The following patch deals with the gcc/testsuite/gm2 ones and
    with the fast_float.h one, ok for trunk?

    Not really sure what we should do in the GmcOptions.c case
    (perhaps obfuscate it in the source somehow by splitting
    the string literals into different substrings
    Perhaps "Copy" "right (" "C) ''..." would do it?  Or do we want
    to bump there each year (manually or by the script)?
    E.g. in gcc.cc we have
          printf ("Copyright %s 2023 Free Software Foundation, Inc.\n",
                  _("(C)"));
    which also prints (C) nicer in Unicode if possible and is updated
    by hand each year.

    I have no idea about the libphobos case, we have tons of
    libphobos/src/std/format/spec.d:Copyright: Copyright The D Language
Foundation 2000-2013.
    libphobos/src/std/random.d:Copyright: Copyright Andrei Alexandrescu 2008 -
2009, Joseph Rushton Wakeling 2012.
    etc. lines and those aren't reported as errors.

    And the last one is that I think for The GCC developers we should treat it
    similarly like FSF and bump copyright on it.
    Would
            canon_gcc = 'The GCC developers'
            self.add_package_author ('The GCC developers', canon_gcc)
            self.add_package_author ('The GCC Developers', canon_gcc)
    or something similar do the trick?

    2023-01-16  Jakub Jelinek  <jakub@redhat.com>

            PR other/108413
            * update-copyright.py (TestsuiteFilter): Add .mod and .rs
extensions.
            (GCCCopyright): Add 'The fast_float authors' as external author.

  parent reply	other threads:[~2023-01-16 10:04 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 ` cvs-commit at gcc dot gnu.org [this message]
2023-01-16 10:08 ` [Bug other/108413] " redi at gcc dot gnu.org
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-7Wl9EmpR0Q@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).