This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Acceptance criteria for the git conversion
- From: Richard Earnshaw <Richard dot Earnshaw at foss dot arm dot com>
- To: Mikhail Maltsev <maltsevm at gmail dot com>, esr at thyrsus dot com, gcc at gcc dot gnu dot org
- Date: Tue, 01 Sep 2015 15:41:56 +0100
- Subject: Re: Acceptance criteria for the git conversion
- Authentication-results: sourceware.org; auth=none
- References: <20150901105414 dot GA30270 at thyrsus dot com> <55E5B5A2 dot 7070509 at gmail dot com>
On 01/09/15 15:26, Mikhail Maltsev wrote:
> On 09/01/2015 01:54 PM, Eric S. Raymond wrote:
>> With the machinery for the git conversion now in reasonable shape, it's
>> time to ask GCC's developers in general: what do you want this
>> conversion to accomplish?
> There was some discussion concerning file renaming:
> https://gcc.gnu.org/ml/gcc/2015-04/msg00175.html
>
> I think using different extensions for C and C++ code is a good thing (because having
> C++ code in ".c" files is confusing both for humans and for tools), and probably
> moving to git is a good occasion for such rename.
> I could take care of performing this change (i.e. make a list of C++ files with .c
> extension, fix build scripts, run some tests), if it is acceptable.
>
Renaming the files during the conversion is clearly *not* the right
thing to do: it would break all builds of old code.
Whether the renames should be done post conversion is a completely
different question. Personally, I don't see the point.
R.