public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Philipp Thomas <pthomas@suse.de>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: fortran/5558: Error in POT file
Date: Fri, 01 Feb 2002 15:06:00 -0000 [thread overview]
Message-ID: <20020201230603.23388.qmail@sources.redhat.com> (raw)
The following reply was made to PR fortran/5558; it has been noted by GNATS.
From: Philipp Thomas <pthomas@suse.de>
To: Toon Moene <toon@moene.indiv.nluug.nl>
Cc: toon@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Subject: Re: fortran/5558: Error in POT file
Date: Fri, 1 Feb 2002 23:55:35 +0100
* Toon Moene (toon@moene.indiv.nluug.nl) [20020201 23:50]:
> However, my question was: Is this something that should be repaired in
> gcc.pot, or is it something that should be repaired in the program that
> generates gcc.pot.
Neither ;-) The respective lines in the *sources* have to be marked with
that comment :( See the patch I sent on how it has to be done.
Philipp
--
Philipp Thomas <pthomas@suse.de>
Development, SuSE GmbH, Deutscherrnstr. 15-19, D-90429 Nuremberg, Germany
Penguins shall save the dinosaurs
-- Handelsblatt about Linux on S/390
next reply other threads:[~2002-02-01 23:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-01 15:06 Philipp Thomas [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-02-04 15:29 pthomas
2002-02-01 16:16 Martin v. Loewis
2002-02-01 14:56 Toon Moene
2002-02-01 13:56 Philipp Thomas
2002-02-01 13:26 Toon Moene
2002-02-01 6:16 Philipp Thomas
2002-02-01 6:09 toon
2002-02-01 1:26 Martin v. Loewis
2002-01-31 17:06 Zack Weinberg
2002-01-31 16:36 Martin v. Loewis
2002-01-31 15:56 Zack Weinberg
2002-01-31 13:06 martin
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=20020201230603.23388.qmail@sources.redhat.com \
--to=pthomas@suse.de \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@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).