From: Milan Zamazal <pdm@zamazal.org>
To: Bill Moseley <moseley@hank.org>
Cc: help-gnats@gnu.org
Subject: Re: Parsing bug reports for indexing
Date: Sun, 23 Dec 2001 12:44:00 -0000 [thread overview]
Message-ID: <87wuzdrjjc.fsf@blackbird.zamazal.org> (raw)
Message-ID: <20011223124400.OfQYTCw3Xq7c-WHegGC2T6XPYsNmmQnF3Z9-VZaNVdw@z> (raw)
In-Reply-To: <3.0.3.32.20011221120232.02696fc0@pop3.hank.org>
>>>>> "BM" == Bill Moseley <moseley@hank.org> writes:
BM> but I'm not clear on all the possible fields (e.g. Audit-Trail)
BM> that might be in a bug report.
In GNATS 4, there can be any fields there. The fields are configured in
`dbconfig', see the corresponding manual entry. Depending on your
needs, you can just consider field identifiers (`>IDENTIFIER:') or parse
dbconfig or use the information provided by gnatsd.
Regards,
Milan Zamazal
--
"Having GNU Emacs is like having a dragon's cave of treasures."
Robert J. Chassell
_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://mail.gnu.org/mailman/listinfo/help-gnats
next prev parent reply other threads:[~2001-12-23 12:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-15 3:40 Bill Moseley
2001-11-19 7:20 ` Milan Zamazal [this message]
2001-12-23 12:44 ` Milan Zamazal
2001-12-21 12:06 ` Bill Moseley
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=87wuzdrjjc.fsf@blackbird.zamazal.org \
--to=pdm@zamazal.org \
--cc=help-gnats@gnu.org \
--cc=moseley@hank.org \
/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).