From: Steinar Bang <sb@dod.no>
Subject: Re: How about a Gnus Bugzilla?
Date: Fri, 15 Oct 2004 07:16:59 +0200 [thread overview]
Message-ID: <877jps5zn8.fsf@dod.no> (raw)
In-Reply-To: <sdu0sxyrqg.fsf@wes.hardakers.net>
[-- Attachment #1: Type: text/plain, Size: 474 bytes --]
>>>>> Wes Hardaker <wes@hardakers.net>:
>>>>> On Thu, 14 Oct 2004 21:12:28 +0200, Steinar Bang <sb@dod.no> said:
Steinar> An nnzilla backend, perhaps? I'm not sure I have an idea
Steinar> about how it should behave, though.
> I have a nnsf (sourceforge) backend coded... Recent html broke it,
> however, but I liked it before I stopped having time to work on it...
Bugzilla has an XML output, that may be easier to use, and to ad-hoc
parse XML. The DTD is attached.
[-- Attachment #2: Bugzilla XML format DTD --]
[-- Type: text/plain, Size: 1851 bytes --]
<!-- Avoid having PSGML complain about these being undefined -->
<!ENTITY amp "&"> <!-- AMPERSAND -->
<!ENTITY lt "`"> <!-- LESS-THAN SIGN -->
<!ENTITY gt ">"> <!-- GREATER-THAN SIGN -->
<!ELEMENT bugzilla (bug+)>
<!ATTLIST bugzilla
version CDATA #REQUIRED
urlbase CDATA #REQUIRED
maintainer CDATA #REQUIRED
exporter CDATA #IMPLIED
>
<!ELEMENT bug (bug_id, (bug_status, product, priority, version, rep_platform, assigned_to, delta_ts, component, reporter, target_milestone?, bug_severity, creation_ts, qa_contact?, op_sys, resolution?, bug_file_loc?, short_desc?, keywords*, status_whiteboard?, dependson*, blocks*, cc*, long_desc*, attachment*)?)>
<!ATTLIST bug
error (NotFound | NotPermitted | InvalidBugId) #IMPLIED
>
<!ELEMENT bug_id (#PCDATA)>
<!ELEMENT exporter (#PCDATA)>
<!ELEMENT urlbase (#PCDATA)>
<!ELEMENT bug_status (#PCDATA)>
<!ELEMENT product (#PCDATA)>
<!ELEMENT priority (#PCDATA)>
<!ELEMENT version (#PCDATA)>
<!ELEMENT rep_platform (#PCDATA)>
<!ELEMENT assigned_to (#PCDATA)>
<!ELEMENT delta_ts (#PCDATA)>
<!ELEMENT component (#PCDATA)>
<!ELEMENT reporter (#PCDATA)>
<!ELEMENT target_milestone (#PCDATA)>
<!ELEMENT bug_severity (#PCDATA)>
<!ELEMENT creation_ts (#PCDATA)>
<!ELEMENT qa_contact (#PCDATA)>
<!ELEMENT status_whiteboard (#PCDATA)>
<!ELEMENT op_sys (#PCDATA)>
<!ELEMENT resolution (#PCDATA)>
<!ELEMENT bug_file_loc (#PCDATA)>
<!ELEMENT short_desc (#PCDATA)>
<!ELEMENT keywords (#PCDATA)>
<!ELEMENT dependson (#PCDATA)>
<!ELEMENT blocks (#PCDATA)>
<!ELEMENT cc (#PCDATA)>
<!ELEMENT long_desc (who, bug_when, thetext)>
<!ELEMENT who (#PCDATA)>
<!ELEMENT bug_when (#PCDATA)>
<!ELEMENT thetext (#PCDATA)>
<!ELEMENT attachment (attachid, date, desc, type?, data?)>
<!ELEMENT attachid (#PCDATA)>
<!ELEMENT date (#PCDATA)>
<!ELEMENT desc (#PCDATA)>
<!ELEMENT type (#PCDATA)>
<!ELEMENT data (#PCDATA)>
next prev parent reply other threads:[~2004-10-15 5:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-14 11:04 Steinar Bang
2004-10-14 17:51 ` Xavier Maillard
2004-10-14 18:44 ` Ted Zlatanov
2004-10-14 19:17 ` Steinar Bang
2004-10-15 15:08 ` Ted Zlatanov
2004-10-15 19:28 ` Steinar Bang
2004-10-19 13:41 ` Bjørn Mork
2004-10-14 20:14 ` Reiner Steib
2004-10-14 21:31 ` Xavier Maillard
2004-10-15 8:40 ` Adam Sjøgren
2004-10-16 9:03 ` Xavier Maillard
2004-10-14 19:12 ` Steinar Bang
2004-10-14 20:22 ` Wes Hardaker
2004-10-15 5:16 ` Steinar Bang [this message]
2004-10-14 21:50 ` Jesper Harder
2004-10-15 5:27 ` Steinar Bang
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=877jps5zn8.fsf@dod.no \
--to=sb@dod.no \
/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 NNTP newsgroup(s).