From: Timothy Bedding <Timothy.Bedding@btinternet.com>
To: gcc@gcc.gnu.org
Cc: Timothy.Bedding@btinternet.com
Subject: FAQ
Date: Sat, 25 Mar 2000 07:31:00 -0000 [thread overview]
Message-ID: <E12YsZR-00008T-00@spacetime.tim> (raw)
Do I post problems and suggestions with the FAQ-o-matic pages to this list
or to gcc-bugs? Are spelling mistakes worth correcting?
Also, are there any bugs in gcc that I can investigate and
provide descriptions of how to fix without actually providing
the source fix (and thus avoid possible copyright issues)?
Or, all the bugs being handled by someone already?
I am running Debian Linux on X86.
Cordially
Tim
next reply other threads:[~2000-03-25 7:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-25 7:31 Timothy Bedding [this message]
2000-03-25 9:22 ` FAQ Jeffrey A Law
2000-03-25 12:43 ` FAQ Martin v. Loewis
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=E12YsZR-00008T-00@spacetime.tim \
--to=timothy.bedding@btinternet.com \
--cc=gcc@gcc.gnu.org \
/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).