public inbox for insight-prs@sourceware.org help / color / mirror / Atom feed
From: kseitz@sources.redhat.com To: insight-prs@sources.redhat.com, kseitz@sources.redhat.com, sls@usc.edu Subject: Re: insight/229: can't find a usable main.tcl Date: Wed, 18 Jun 2003 01:21:00 -0000 [thread overview] Message-ID: <20030618012117.3421.qmail@sources.redhat.com> (raw) Synopsis: can't find a usable main.tcl State-Changed-From-To: analyzed->closed State-Changed-By: kseitz State-Changed-When: Wed Jun 18 01:21:17 2003 State-Changed-Why: Somehow user got a corrupted gdbtk.ini. Don't know how that happened, but removing the file "fixed" the problem. Should investigate more. http://sources.redhat.com/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=insight&pr=229
next reply other threads:[~2003-06-18 1:21 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-06-18 1:21 kseitz [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-06-13 18:13 Scott, Steven 2003-06-13 17:03 Keith Seitz 2003-06-12 22:33 Keith Seitz 2003-06-12 21:11 kseitz 2003-06-12 21:03 sls
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=20030618012117.3421.qmail@sources.redhat.com \ --to=kseitz@sources.redhat.com \ --cc=insight-gnats@sources.redhat.com \ --cc=insight-prs@sources.redhat.com \ --cc=sls@usc.edu \ /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: linkBe 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).