Re: Bug reduction instructions, draft 2

[Janis Johnson <janis187 at us dot ibm dot com>]

On Fri, Jan 17, 2003 at 01:16:07AM +0100, Gerald Pfeifer wrote:
> On Tue, 14 Jan 2003, Wolfgang Bangerth wrote:
> 
> Please make the link relative, i.e., "bugs.html" or "../bugs.html".

I'll make the bugs directory so we can put this new file there (or you
can, Gerald).

> > +<p>If you're reporting the bug, you've got the choice of starting
> > +with either the original source files or with a preprocessed file.
> > +Both methods are described below.</p>
> 
> I don't fully understand how "If you're reporting the bug" fits in here?

That was because GCC volunteers don't have access to the original files;
the PR is supposed to have only the preprocessed version.  Perhaps "If
you have access to the original source files you've got the choice of
starting either with them or with a preprocessed file."

> > +  <li>Strip as much code as possible from the function in which the
> > +  problem happens.  It's not important if the remaining code doesn't
> > +  make any sense, it only needs to trigger the bug.
> 
> Ah, and now the question: Do we really want to append "-howto" to the name
> of this page? I have a weak preference for htdocs/bugs/minimize.html, but
> I may be easily convinced otherwise.

That was my idea.  It would be nice for them to be consistent, but when
I move reghunt-howto.html to the bugs directory I could change its name
as well.  That file is not yet referenced anywhere, so there shouldn't
be a problem moving and renaming it, should there?

By the way, should we just leave bugs.html where it is?  It sounds like
moving it would be very error-prone.

> (Once we have fixed the name, feel free to commit this, or ask Janis or
> me.)

I like the rest of Gerald's recommendations.

Janis