From: Ralf Corsepius <corsepiu@faw.uni-ulm.de>
To: mdejong@sources.redhat.com, sourcenav@sources.redhat.com
Subject: Re: sourcenav/59
Date: Thu, 07 Jun 2001 01:11:00 -0000 [thread overview]
Message-ID: <3B1F376A.9631F851@faw.uni-ulm.de> (raw)
In-Reply-To: <20010607025442.15865.qmail@sourceware.cygnus.com>
mdejong@sources.redhat.com wrote:
>
> Synopsis: parsers/cpp/* contains comments in a foreign language
>
> State-Changed-From-To: open->closed
> State-Changed-By: mdejong
> State-Changed-When: Wed Jun 6 19:54:42 2001
> State-Changed-Why:
> This is not a bug report! Simple complaints should
> be directed to the mailing list.
What?
> http://sources.redhat.com/cgi-bin/gnatsweb.pl?cmd=view&pr=59&database=sourcenav
Unreadable source-code is not supposed to be bugs?
Sorry, but I do not share this opinion. IMO, it's a matter of
code-quality and in open source are part of the documentation.
Ralf
next parent reply other threads:[~2001-06-07 1:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010607025442.15865.qmail@sourceware.cygnus.com>
2001-06-07 1:11 ` Ralf Corsepius [this message]
2001-06-07 11:58 ` sourcenav/59 Mo DeJong
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=3B1F376A.9631F851@faw.uni-ulm.de \
--to=corsepiu@faw.uni-ulm.de \
--cc=mdejong@sources.redhat.com \
--cc=sourcenav@sources.redhat.com \
/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).