This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Heads up: please help documenting *internal* GCC changes for 4.6

On Jan 28, 2011, at 8:04 AM, Laurynas Biveinis wrote:

> 2011/1/28 Basile Starynkevitch <basile@starynkevitch.net>:
>>> Its intention is to mention noteworthy internal changes, i.e. changes
>>> interesting for, say, maintainers of backends/frontends outside the
>>> tree, and of course plugin developers upgrading from 4.5 to 4.6.
>>> 
>> 
>> 
>> I am not sure to understand what is the social rules to modify that. I
>> suppose that any patch to that page should be approved with the same
>> strong process as patches to trunk code?
> 
> It needs to be reviewed, but it's much easier IMHO.

I'm wondering if it would be helpful for the internal changes to be documented in a separate file, rather than in the same file as the user changes.  That makes it more obvious what documentation is being touched.

	paul
Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]