public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Stefan Michel <smichel@lucent.com>
To: gcc-help@gcc.gnu.org
Subject: list of warnings
Date: Wed, 21 Nov 2001 12:30:00 -0000	[thread overview]
Message-ID: <3C049585.C106B087@lucent.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 282 bytes --]

Hi,

is there a list of warnings that gcc can produce available?

Thanks,
  Stefan

-- 
Stefan Michel, Lucent Technologies Network Systems GmbH, Dept. SW13,
Thurn-und-Taxis-Str. 10, 90411 Nuernberg, Germany
Phone: +49 911 526-4482     Fax: +49 911 526-3328
mailto:smichel@lucent.com

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 1538 bytes --]

WARNING: multiple messages have this Message-ID

From: Stefan Michel <smichel@lucent.com>
To: gcc-help@gcc.gnu.org
Subject: list of warnings
Date: Tue, 27 Nov 2001 23:45:00 -0000	[thread overview]
Message-ID: <3C049585.C106B087@lucent.com> (raw)
Message-ID: <20011127234500.EwT7IYUK17-EWCXKJwM21aIytn72SNVxJz8-7971sZ4@z> (raw)

[-- Attachment #1: Type: text/plain, Size: 350 bytes --]

Hi,

is there a list of warnings that gcc can produce available?

Thanks,
  Stefan

-- 
Stefan Michel, Lucent Technologies Network Systems GmbH, Dept. SW13,
Thurn-und-Taxis-Str. 10, 90411 Nuernberg, Germany
Phone: +49 911 526-4482     Fax: +49 911 526-3328
mailto:smichel@lucent.com
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature


[-- Attachment #2: smime.p7s --]
[-- Type: application/octet-stream, Size: 1538 bytes --]

             reply	other threads:[~2001-11-28  7:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-21 12:30 Stefan Michel [this message]
2001-11-21 23:24 ` Andrea 'Fyre Wyzard' Bocci
2001-11-28 14:56   ` Andrea 'Fyre Wyzard' Bocci
2001-11-27 23:45 ` Stefan Michel

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=3C049585.C106B087@lucent.com \
    --to=smichel@lucent.com \
    --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).