From: Carl-Johan Sveningsson <woc@wlug.westbo.se>
To: bug-gnats@gnu.org, gnats-devel@sourceware.cygnus.com,
mstachow@alum.mit.edu
Subject: Gnatsweb - problem resolved
Date: Mon, 10 Jul 2000 07:59:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.21.0007101701080.31476-100000@wlug.westbo.se> (raw)
Hello all.
My apologies, the problem I mentioned in the earlier letters is now
resolved, it seemed to be a problem with the compiled-in paths to
categories and my handling of them...
Anyway, now it works, and gnatsweb is running. :-)
Thanks all anyway for a nice bugtracking tool.
/Carl-Johan Sveningsson
--
"...you look strong enough to pull the ears off a Gundark."
ICQ# 2357535
http://come.to/woc/
http://wlug.westbo.se/
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GSS/CS/P d(++,--)>--- s-: a--- C(++++,!) UL+++ P+++>$ L++ E-$ W++(@)
N? o?>++++ K? w-- !O M- V? PS++(@) PE- Y? PGP?>++ t->++ 5?>+++ X+ R-
tv->! b+>+++ DI++ D+ G e+>+++$ h-->(+,----) r>(+++,---) y+++++>**
------END GEEK CODE BLOCK------
reply other threads:[~2000-07-10 7:59 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=Pine.LNX.4.21.0007101701080.31476-100000@wlug.westbo.se \
--to=woc@wlug.westbo.se \
--cc=bug-gnats@gnu.org \
--cc=gnats-devel@sourceware.cygnus.com \
--cc=mstachow@alum.mit.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: 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).