From: <baltasar@nm.ru>
To: gcc-help@gcc.gnu.org
Subject: Using GCC in commercial products
Date: Mon, 07 Apr 2008 08:55:00 -0000 [thread overview]
Message-ID: <20080407084028.22937.qmail@flock1.newmail.ru> (raw)
Hello,
We're planning to use GCC 3.2.x compiler for building our product.
Should we mention about using GCC in our documentation?
reply other threads:[~2008-04-07 8:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20080407084028.22937.qmail@flock1.newmail.ru \
--to=baltasar@nm.ru \
--cc=gcc-help@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).