public inbox for insight-prs@sourceware.org
help / color / mirror / Atom feed
From: kseitz@sources.redhat.com
To: bobwirka@yahoo.com, insight-prs@sourceware.cygnus.com,
kseitz@sources.redhat.com, nobody@sourceware.cygnus.com
Subject: Re: insight/86: Make fails at tclEnv.c; CCHAR unrecognized
Date: Fri, 04 Jan 2002 14:17:00 -0000 [thread overview]
Message-ID: <20020104221735.10613.qmail@sources.redhat.com> (raw)
Synopsis: Make fails at tclEnv.c; CCHAR unrecognized
Responsible-Changed-From-To: unassigned->kseitz
Responsible-Changed-By: kseitz
Responsible-Changed-When: Fri Jan 4 14:17:35 2002
Responsible-Changed-Why:
mine
State-Changed-From-To: open->feedback
State-Changed-By: kseitz
State-Changed-When: Fri Jan 4 14:17:35 2002
State-Changed-Why:
Is this still a problem with 5.1?
http://sources.redhat.com/cgi-bin/gnatsweb.pl?cmd=view&pr=86&database=insight
next reply other threads:[~2002-01-04 22:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-04 14:17 kseitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-04-01 11:43 bobwirka
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=20020104221735.10613.qmail@sources.redhat.com \
--to=kseitz@sources.redhat.com \
--cc=bobwirka@yahoo.com \
--cc=insight-prs@sourceware.cygnus.com \
--cc=nobody@sourceware.cygnus.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).