public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Daniel Berlin <dberlin@dberlin.org>
To: Volker Reichelt <reichelt@igpm.rwth-aachen.de>
Cc: gcc@gcc.gnu.org, bangerth@ices.utexas.edu, giovannibajo@libero.it
Subject: Re: Suggested Bugzilla improvements
Date: Tue, 13 May 2003 16:53:00 -0000	[thread overview]
Message-ID: <794E48E5-8563-11D7-8378-000A95A34564@dberlin.org> (raw)
In-Reply-To: <200305131558.h4DFwgNZ011904@relay.rwth-aachen.de>


On Tuesday, May 13, 2003, at 11:58  AM, Volker Reichelt wrote:

> On 13 May, Daniel Berlin wrote:
>
>>> * What's the purpose of the URL field?
>>>   Sending an URL instead of a preprocessed file is a no-no.
>>>   Doesn't that encourage users to send us URLs?
>> It was there, i never removed it, and probably won't (though i could
>> make it invisible if you like).
>
> Please make it invisible (that's at least my opinion).
Done. It's now invisible.

>>> * The page "bug_status.html" needs updating, especially the parts 
>>> about
>>>   the Platform/Operating System.
>>>
>> Thanks, i'll do it.
>
> The page should probably be merged with "bugs/management.html" somehow
> when Bugzilla goes online. One page of documentation should be enough.
>
Yup.
I seem to have lost the message saying what other docs on the gcc 
website i should update when it goes live.
Can someone give me the list again, if it's not too much trouble?
I'm not talking about Bugzilla's docs, i mean the gcc web pages.


I seem to remember that we already took care of the internal-only docs 
related to branch and release creation.
--Dan
> Regards,
> Volker
>
>

  reply	other threads:[~2003-05-13 16:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-13 16:07 Volker Reichelt
2003-05-13 16:53 ` Daniel Berlin [this message]
2003-05-13 20:50   ` Joseph S. Myers
2003-05-14 15:07     ` Gerald Pfeifer
  -- strict thread matches above, loose matches on Subject: below --
2003-05-13  9:19 Volker Reichelt
2003-05-13 10:20 ` Joseph S. Myers
2003-05-13 14:39   ` Daniel Berlin
2003-05-13 14:52     ` Joseph S. Myers
2003-05-13 15:33       ` Daniel Berlin
2003-05-13 14:41 ` Daniel Berlin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=794E48E5-8563-11D7-8378-000A95A34564@dberlin.org \
    --to=dberlin@dberlin.org \
    --cc=bangerth@ices.utexas.edu \
    --cc=gcc@gcc.gnu.org \
    --cc=giovannibajo@libero.it \
    --cc=reichelt@igpm.rwth-aachen.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).