This is the mail archive of the gcc-patches@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: Clarify rules for testing patches


On Thu, Nov 29, 2001 at 12:44:13AM +0000, Joseph S. Myers wrote:
> On Wed, 28 Nov 2001, Zack Weinberg wrote:
> 
> > +<p>If your change is to code that is not in a front-end, or is to
> > +the C front-end, you must perform a complete build of GCC and the
> 
> The convention is that the noun is spelt "front end".

"front-end" was how the original text spelled it, but I've changed
this in my tree.

> > -<p>Note that when you check in changes to our web pages, these will
> > -automatically be checked out into the web server's data area.</p>
> > +<p>When you check in changes to our web pages, they will automatically
> > +be checked out into the web server's data area.</p>
> 
> If you check in changes to style.mhtml, does this cause the other web
> pages to be automatically regenerated?

I don't know.  Gerald?

> > +<p>When you post your change to <code>gcc-patches</code>, indicate
> > +what platform you have used for testing.</p>
> 
> There should be a note somewhere that "platform" means an exact target
> triplet rather than a vague description such as "Alpha" or "x86 Linux".

Like this?

+<p>When you post your change to <code>gcc-patches</code>, state
+the canonical name(s) of the system(s) you have used for testing.</p>

zw


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