From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4849 invoked from network); 23 Dec 2001 20:44:52 -0000 Received: from unknown (HELO fencepost.gnu.org) (199.232.76.164) by sources.redhat.com with SMTP; 23 Dec 2001 20:44:52 -0000 Received: from localhost ([127.0.0.1] helo=fencepost.gnu.org) by fencepost.gnu.org with esmtp (Exim 3.22 #1 (Debian)) id 16IFDN-0006wd-00; Sun, 23 Dec 2001 15:27:21 -0500 Received: from sokol.skynet.cz ([193.165.254.8]) by fencepost.gnu.org with esmtp (Exim 3.22 #1 (Debian)) id 16IFBc-0006rz-00 for ; Sun, 23 Dec 2001 15:25:32 -0500 X-Envelope-To: help-gnats@gnu.org Received: from blackbird.zamazal.org (mail@asasync61.skynet.cz [193.165.192.161]) by sokol.skynet.cz (8.9.3/8.9.3) with ESMTP id VAA21051; Sun, 23 Dec 2001 21:25:00 +0100 (envelope-from pdm@zamazal.org) Received: from pdm by blackbird.zamazal.org with local (Exim 3.32 #1 (Debian)) id 16IFAb-0001eE-00; Sun, 23 Dec 2001 21:24:29 +0100 To: Bill Moseley Cc: help-gnats@gnu.org Subject: Re: Parsing bug reports for indexing References: <3.0.3.32.20011221120232.02696fc0@pop3.hank.org> X-Face: >kl&pL}(a*u\BCj7Q,\Yoq35~,4dAu"CPGaJ[ahMli9uu#aF7dWxc3L.eaK2RWRU|',E+. -':&gJ-JAZ/N$f^4-3?G7M&Knna[A=lJ$}^!%@vuvulVl6-)x.V8RZ7fW9< From: Milan Zamazal In-Reply-To: <3.0.3.32.20011221120232.02696fc0@pop3.hank.org> Message-ID: <87wuzdrjjc.fsf@blackbird.zamazal.org> User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: help-gnats-admin@gnu.org Errors-To: help-gnats-admin@gnu.org X-BeenThere: help-gnats@gnu.org X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: General discussion about GNU GNATS List-Archive: Date: Mon, 19 Nov 2001 07:20:00 -0000 X-SW-Source: 2001-q4/txt/msg00145.txt.bz2 >>>>> "BM" == Bill Moseley 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 From mboxrd@z Thu Jan 1 00:00:00 1970 From: Milan Zamazal To: Bill Moseley Cc: help-gnats@gnu.org Subject: Re: Parsing bug reports for indexing Date: Sun, 23 Dec 2001 12:44:00 -0000 Message-ID: <87wuzdrjjc.fsf@blackbird.zamazal.org> References: <3.0.3.32.20011221120232.02696fc0@pop3.hank.org> X-SW-Source: 2001-q4/msg00266.html Message-ID: <20011223124400.OfQYTCw3Xq7c-WHegGC2T6XPYsNmmQnF3Z9-VZaNVdw@z> >>>>> "BM" == Bill Moseley 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