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:23:52 +0000 [thread overview]
Message-ID: <bug-108413-4-xbpHth5GRL@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 #5 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:c841bde5ac2bd8915ecc974ff7623c8954fc1cf3
commit r13-5188-gc841bde5ac2bd8915ecc974ff7623c8954fc1cf3
Author: Jakub Jelinek <jakub@redhat.com>
Date: Mon Jan 16 11:22:09 2023 +0100
riscv: Fix up Copyright lines [PR108413]
These 2 files had incorrectly formatted Copyright lines (no space between
Copyright and (C)) which makes update-copyright.py upset.
2023-01-16 Jakub Jelinek <jakub@redhat.com>
PR other/108413
* config/riscv/riscv-vsetvl.h: Add space in between Copyright and
(C).
* config/riscv/riscv-vsetvl.cc: Likewise.
next prev parent reply other threads:[~2023-01-16 10:23 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
2023-01-16 10:23 ` cvs-commit at gcc dot gnu.org [this message]
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-xbpHth5GRL@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).