Parsing bug reports for indexing

Parsing bug reports for indexing

[Bill Moseley]

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

Re: Parsing bug reports for indexing

[Milan Zamazal]

>>>>> "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

Parsing bug reports for indexing

[Bill Moseley]

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

Re: Parsing bug reports for indexing

[Milan Zamazal]

>>>>> "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