This is the mail archive of the
mailing list for the GCC project.
Re: is it time to mass change from .c to .cc in gcc/ ?
- From: Mikhail Maltsev <maltsevm at gmail dot com>
- To: Manuel LÃpez-IbÃÃez <lopezibanez at gmail dot com>, Trevor Saunders <"tbsaunde at tbsaunde dot org">, Richard Biener <"richard dot guenther at gmail dot com">
- Cc: GCC Development <"gcc at gcc dot gnu dot org">
- Date: Thu, 16 Apr 2015 08:30:53 +0300
- Subject: Re: is it time to mass change from .c to .cc in gcc/ ?
- Authentication-results: sourceware.org; auth=none
- References: <20150414052030 dot GE8601 at tsaunders-iceball dot corp dot tor1 dot mozilla dot com> <CAFiYyc0RydCJhmSdB6_uDY+SpTAYC2RN_d17bdZR=ug7ThFN2w at mail dot gmail dot com> <20150415000911 dot GA30215 at tsaunders-iceball dot corp dot tor1 dot mozilla dot com> <552E3512 dot 2000506 at gmail dot com> <552E9016 dot 6010107 at gmail dot com>
On 15.04.2015 19:21, Manuel LÃpez-IbÃÃez wrote:
> The "right" steps to see progress:
> 1. You think that some concrete change may improve GCC, for example, to
> move vec.h and is-a.h to some gcc/include/core. Ask if the key people
> (Global Reviewers in this case) will accept this change.
> 2.1 If not, then goto 1 and think about something else (or perhaps
> people misunderstood what you meant?
Well, sort of :). I did not mean that I want to try to design the
structure for GCC source code tree. I was talking about documentation
> Just do it.
> Sent a patch for gccint.texi or create a webpage in the wiki
> to draft it or just draft it in plain-text and send it to the mailing
Started with the latter. By the way, what is the policy concerning
getting write access to the wiki?