From: Yngve Svendsen <yngve.svendsen@clustra.com>
To: nick@brainstorm.co.uk, gnats-devel@sources.redhat.com
Subject: Re: gnatsweb plans?
Date: Mon, 11 Jun 2001 13:35:00 -0000 [thread overview]
Message-ID: <5.1.0.14.2.20010611223508.00b78b10@10.10.1.1> (raw)
In-Reply-To: <3B24B129.484A3A3@brainstorm.co.uk>
At 12:53 11.06.2001 +0100, nick@brainstorm.co.uk wrote:
>Are there plans for gnatsweb to use gnatsd for problem submission? Is
>this possible with the gnatsd of v4.0?
Yes, that is indeed what Gnatsweb for GNATS 4 does. By default, all of
Gnatsweb's communication with GNATS 4 is done directly with gnatsd.
Yngve Svendsen
Gnatsweb maintainer
prev parent reply other threads:[~2001-06-11 13:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-04 13:04 Announcing gnatsweb 2.8.1 Yngve Svendsen
2001-06-07 4:51 ` Gerald Pfeifer
2001-06-07 7:38 ` gnatsd: Could not resolve database alias? (and suggestions) nick
2001-06-07 7:49 ` Yngve Svendsen
2001-06-07 8:00 ` nick
2001-06-07 8:04 ` Yngve Svendsen
2001-06-11 4:54 ` gnatsweb plans? nick
2001-06-11 13:35 ` Yngve Svendsen [this message]
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=5.1.0.14.2.20010611223508.00b78b10@10.10.1.1 \
--to=yngve.svendsen@clustra.com \
--cc=gnats-devel@sources.redhat.com \
--cc=nick@brainstorm.co.uk \
/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).