From: "Martin Liška" <mliska@suse.cz>
To: Toon Moene <toon@moene.org>, Martin Jambor <mjambor@suse.cz>,
GCC Mailing List <gcc@gcc.gnu.org>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>, gfortran <fortran@gcc.gnu.org>
Subject: Re: [PATCH] Mass rename of C++ .c files to .cc suffix
Date: Tue, 11 Jan 2022 16:50:02 +0100 [thread overview]
Message-ID: <713a96b5-b82e-ffd7-d03b-7e05a4dede9e@suse.cz> (raw)
In-Reply-To: <68946bf6-4b2f-b8f3-20b3-5cf3f2fd611c@moene.org>
On 1/11/22 16:48, Toon Moene wrote:
> On 1/11/22 13:56, Martin Liška wrote:
>
>> Patch can bootstrap on x86_64-linux-gnu and survives regression tests.
>> Plus it survives build of all FEs (--enable-languages=all) on x86_64-linux-gnu
>> and I've built all cross compilers.
>
> Does this also rename .c files in the fortran and libgfortran directories ?
Hello.
Yes, it does the first one.
>
> I would recommend to send this message to the fortran@gcc.gnu.org list too, then.
>
> Not everyone reads the gcc and gcc-patches lists ...
CCing the list now.
Thanks,
Martin
>
> Kind regards,
>
next prev parent reply other threads:[~2022-01-11 15:50 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-07 10:25 Mass rename of C++ .c files to .cc suffix? Martin Jambor
2022-01-07 10:33 ` Richard Sandiford
2022-01-07 10:44 ` Andrew Pinski
2022-01-07 10:51 ` Jonathan Wakely
2022-01-07 10:51 ` Jakub Jelinek
2022-01-07 11:05 ` Jonathan Wakely
2022-01-07 12:55 ` Martin Liška
2022-01-07 14:42 ` Iain Sandoe
2022-01-07 14:49 ` Jeff Law
2022-01-07 15:45 ` Jeff Law
2022-01-07 15:59 ` David Malcolm
2022-01-07 17:31 ` Jonathan Wakely
2022-01-10 9:11 ` Martin Liška
2022-01-07 18:33 ` Alexandre Oliva
2022-01-07 19:01 ` Jakub Jelinek
2022-01-11 12:56 ` [PATCH] Mass rename of C++ .c files to .cc suffix Martin Liška
2022-01-11 15:48 ` Toon Moene
2022-01-11 15:50 ` Martin Liška [this message]
2022-01-11 15:56 ` Jakub Jelinek
2022-01-11 16:03 ` Martin Liška
2022-01-11 16:16 ` Jakub Jelinek
2022-01-12 8:58 ` Martin Liška
2022-01-12 15:54 ` [PATCH] git-backport: support renamed .cc files in commit message Martin Liška
2022-01-14 7:44 ` Bernhard Reutner-Fischer
2022-01-14 15:26 ` Martin Liška
2022-01-17 21:26 ` Martin Liška
2022-01-18 19:10 ` Harald Anlauf
2022-01-19 8:07 ` Martin Liška
2022-01-11 18:00 ` [PATCH] Mass rename of C++ .c files to .cc suffix Harald Anlauf
2022-01-11 18:00 ` Harald Anlauf
2022-01-11 18:23 ` Jonathan Wakely
2022-01-11 18:36 ` Jakub Jelinek
2022-01-13 11:01 ` [ANNOUNCEMENT] Mass rename of C++ .c files to .cc suffix is going to happen on Jan 17 evening UTC TZ Martin Liška
2022-01-17 21:41 ` Martin Liška
2022-01-18 8:36 ` Eric Botcazou
2022-01-18 8:39 ` Martin Liška
2022-01-18 8:46 ` Eric Botcazou
2022-01-18 8:53 ` Richard Biener
2022-01-18 9:08 ` Martin Liška
2022-01-18 9:13 ` Jakub Jelinek
2022-01-18 9:43 ` Martin Liška
2022-01-18 13:10 ` Richard Earnshaw
2022-01-18 13:16 ` Martin Liška
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=713a96b5-b82e-ffd7-d03b-7e05a4dede9e@suse.cz \
--to=mliska@suse.cz \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=mjambor@suse.cz \
--cc=toon@moene.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).