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

Basile Starynkevitch <basile@starynkevitch.net> writes:

> 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?

I would say that any gcc maintainer may update the changes file without
explicit review.  The patch must be valid HTML, and Gerald runs a script
which verifies that.  Patches must be sent to gcc-patches@gcc.gnu.org.

Only make changes that are correct.  If you feel uncertain, you should
get a review.  That review can come from any other gcc maintainer.

(Anyone: please let me know if you disagree with the above.)

> I am not sure to understand the technical ways to modify that; is CVS
> still mandatory?

Yes.

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