From: Bill Moseley <moseley@hank.org>
To: help-gnats@gnu.org
Subject: Parsing bug reports for indexing
Date: Fri, 21 Dec 2001 12:06:00 -0000 [thread overview]
Message-ID: <3.0.3.32.20011221120232.02696fc0@pop3.hank.org> (raw)
Message-ID: <20011221120600.sXnMbXFHjw6csTfvSas1qDHhNYJa8iCWdqRRDEQqaek@z> (raw)
Hi,
I need some code to parse bug reports for indexing by swish-e, and I'm
trying to avoid reinventing the wheel.
I'm wondering if anyone has written a perl module for parsing the reports,
cleaning up any MIME (and Outlook junk), and which provides an OO interface.
Anyone done this already?
If not, I assume I can just use basic MIME tools to do this, but I'm not
clear on all the possible fields (e.g. Audit-Trail) that might be in a bug
report.
The goal is to parse out dates, status, author, subject, and body text, and
perhaps replies to the report.
Thanks,
Bill Moseley
mailto:moseley@hank.org
_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://mail.gnu.org/mailman/listinfo/help-gnats
next reply other threads:[~2001-12-21 12:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-15 3:40 Bill Moseley [this message]
2001-11-19 7:20 ` Milan Zamazal
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=3.0.3.32.20011221120232.02696fc0@pop3.hank.org \
--to=moseley@hank.org \
--cc=help-gnats@gnu.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).