From: "Martin Liška" <mliska@suse.cz>
To: Martin Jambor <mjambor@suse.cz>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Mass rename of C++ .c files to .cc suffix
Date: Thu, 13 Jan 2022 11:57:28 +0100 [thread overview]
Message-ID: <b736c9c2-2b2e-f90f-ef97-4af819dd7c8a@suse.cz> (raw)
In-Reply-To: <ri6h7a7ud2k.fsf@suse.cz>
On 1/13/22 11:47, Martin Jambor wrote:
> Hi,
>
> On Tue, Jan 11 2022, Martin Liška wrote:
>> Hello.
>>
>> I've got a patch series that does the renaming. It contains of 2 automatic
>> scripts ([1] and [2]) that were run as:
>>
>> $ gcc-renaming-candidates.py gcc --rename && git commit -a -m 'Rename files.' && rename-gcc.py . -vv && git commit -a -m 'Automatic renaming'
>>
>> The first scripts does the renaming (with a couple of exceptions that are really C files) and saves
>> the renamed files to a file. Then the file is then loaded and replacement of all the renamed files does happen
>> for most of the GCC files ([2]). It basically replaces at \b${old_filename}\b with ${old_filename}c
>> (with some exceptions). That corresponds to patch #1 and #2 and the patches are quite huge.
>>
>> The last piece are manual changes needed for Makefile.in, configure.ac and so on.
>>
>> The git branch can be seen here:
>> https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;a=log;h=refs/users/marxin/heads/cc-renaming
>>
>> and pulled with:
>> $ git fetch refs/users/marxin/heads/cc-renaming
>> $ git co FETCH_HEAD
>>
>
> Thanks for the effort! I looked at the branch and liked what I saw.
Thanks.
> Perhaps only a small nit about the commit message of the 2nd commit
> ("Automatic renaming of .c files to .cc.") which confused me. It does
> not actually rename any files so I would change it to "change references
> to .c files to .cc files" or something like that.
Sure, I'm going to update the commit message.
>
> But I assume the branch will need to be committed squashed anyway, so
> commit message worries might be a bit premature.
No, I would like to commit it as 3 separate commits for this reasons:
- git renaming with 100% match should guarantee git would fully work with merging and stuff like that
- I would like to distinguish manual changes from these that are only a mechanical replacement.
Cheers,
Martin
>
> I am looking forward to seeing it in trunk.
>
> Martin
next prev parent reply other threads:[~2022-01-13 10:57 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ri6mtk7vo41.fsf@suse.cz>
2022-01-11 12:56 ` Martin Liška
2022-01-11 15:48 ` Toon Moene
2022-01-11 15:50 ` Martin Liška
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: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
2022-01-13 10:47 ` [PATCH] Mass rename of C++ .c files to .cc suffix Martin Jambor
2022-01-13 10:57 ` Martin Liška [this message]
2022-01-13 11:14 ` Richard Biener
2022-01-13 11:20 ` Martin Liška
2022-01-13 11:32 ` Jakub Jelinek
2022-01-13 12:20 ` Martin Jambor
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=b736c9c2-2b2e-f90f-ef97-4af819dd7c8a@suse.cz \
--to=mliska@suse.cz \
--cc=gcc-patches@gcc.gnu.org \
--cc=mjambor@suse.cz \
/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).