From: stefan.kaes@portax.com
To: gnats-devel@sources.redhat.com, gnats-devel-owner@sources.redhat.com
Subject: gnatsweb/gnatsd debugging
Date: Fri, 23 Mar 2001 08:38:00 -0000 [thread overview]
Message-ID: <OF77F32D8B.26F1136A-ONC1256A18.005992C1@portax.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 927 bytes --]
I am using gnats113 and gnatsweb2.7beta:
I have the problem that sometimes gnatsweb ist not able edit a problem
report, although all relevant emails are sent that the report was edited.
this seems to happen mostly with reports that contain attachements.
any ideas?
_________________________________
Additional award for portax.com - Top Chemical Content Award
portax.com has received the Top Chemical Content Award for a well
structured and user friendly marketplace, a broad range of daily updated
industry news and value added services. This award is given by Chemie.de a
leading information platform for the chemical and life science industry.
_________________________________
Stefan Kaes
portax.com GmbH
Zielstattstrasse 40, Geb. 16
81379 München
Tel: +49 (0)89 748 99 - 127
Fax: +49 (0)89 748 99 - 111
Mob: +49 (0)172 89 86 401
E-Mail: stefan.kaes@portax.com
Web: http://www.portax.com
reply other threads:[~2001-03-23 8:38 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=OF77F32D8B.26F1136A-ONC1256A18.005992C1@portax.com \
--to=stefan.kaes@portax.com \
--cc=gnats-devel-owner@sources.redhat.com \
--cc=gnats-devel@sources.redhat.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).