public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
* Re: Bug reporting instructions
@ 2003-05-10  3:51 Wolfgang Bangerth
  2003-05-10 10:02 ` Joseph S. Myers
  0 siblings, 1 reply; 3+ messages in thread
From: Wolfgang Bangerth @ 2003-05-10  3:51 UTC (permalink / raw)
  To: Dara Hazeghi, gcc; +Cc: Gerald Pfeifer



> http://gcc.gnu.org/bugs.html#where mentions both GNATS and gcc-bugs. But 
> http://gcc.gnu.org/onlinedocs/g77/Bug-Lists.html , 
> http://gcc.gnu.org/onlinedocs/gcc/Bug-Lists.html and probably all the 
> others only mention gcc-bugs. Should this be updated?

The second one is actually quite funny, since it mentions sending in bug 
reports on paper to the FSF :-) I think all these places should be updated 
to read like the first one, and the FSF address should go (clearly an 
outdated method; we might suggest using carrier pidgeons instead).

Gerald, unless you do it over the weekend, I'll take care of it on Monday 
when I'm back in office. Just let me know.

W.

-------------------------------------------------------------------------
Wolfgang Bangerth              email:            bangerth@ices.utexas.edu
                               www: http://www.ices.utexas.edu/~bangerth/


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Bug reporting instructions
  2003-05-10  3:51 Bug reporting instructions Wolfgang Bangerth
@ 2003-05-10 10:02 ` Joseph S. Myers
  0 siblings, 0 replies; 3+ messages in thread
From: Joseph S. Myers @ 2003-05-10 10:02 UTC (permalink / raw)
  To: Wolfgang Bangerth; +Cc: Dara Hazeghi, gcc, Gerald Pfeifer

On Fri, 9 May 2003, Wolfgang Bangerth wrote:

> > http://gcc.gnu.org/bugs.html#where mentions both GNATS and gcc-bugs. But 
> > http://gcc.gnu.org/onlinedocs/g77/Bug-Lists.html , 
> > http://gcc.gnu.org/onlinedocs/gcc/Bug-Lists.html and probably all the 
> > others only mention gcc-bugs. Should this be updated?
> 
> The second one is actually quite funny, since it mentions sending in bug 
> reports on paper to the FSF :-) I think all these places should be updated 
> to read like the first one, and the FSF address should go (clearly an 
> outdated method; we might suggest using carrier pidgeons instead).
> 
> Gerald, unless you do it over the weekend, I'll take care of it on Monday 
> when I'm back in office. Just let me know.

The bulk of the residual parts of bugreport.texi should be merged into the
online documentation (where the information that is still useful isn't
already there - and some care must be taken to avoid the online
documentation getting too long) and replaced with just a link to the
online documentation (and maybe a note that this online documentation is
distributed with release tarballs (as both text and HTML), so people can
read it offline then submit bug reports offline with gccbug).

Much the same applies to the Fortran bug reporting documentation - which
is largely derived from an older, longer, version of the main GCC bug
reporting documentation - except that there may be some Fortran-specific
details to add to the online documentation.

-- 
Joseph S. Myers
jsm28@cam.ac.uk

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Bug reporting instructions
@ 2003-05-10  3:32 Dara Hazeghi
  0 siblings, 0 replies; 3+ messages in thread
From: Dara Hazeghi @ 2003-05-10  3:32 UTC (permalink / raw)
  To: gcc

Hello,

http://gcc.gnu.org/bugs.html#where mentions both GNATS and gcc-bugs. 
But http://gcc.gnu.org/onlinedocs/g77/Bug-Lists.html , 
http://gcc.gnu.org/onlinedocs/gcc/Bug-Lists.html and probably all the 
others only mention gcc-bugs. Should this be updated?

Thanks,

Dara

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2003-05-10 10:02 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-05-10  3:51 Bug reporting instructions Wolfgang Bangerth
2003-05-10 10:02 ` Joseph S. Myers
  -- strict thread matches above, loose matches on Subject: below --
2003-05-10  3:32 Dara Hazeghi

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).