Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Gnus interface to Bugzilla?
Date: Thu, 13 Apr 2006 13:45:10 +0200	[thread overview]
Message-ID: <m3odz5pum1.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <m37j5trheg.fsf@quimbies.gnus.org>

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Does Bugzilla have a programmable interface, or does one have to parse
> the HTML?

Newer versions of Bugzilla allow setting the ctype={format} parameter,
så one can get out csv/xml/whatever data.

So parsing Bugzilla should be pretty easy.  However, the listing of
the bugs in question doesn't include how many responses there have
been, so you won't get the most important thing in a news reader --
notification that there are new messages to read.

Well, without actually querying each bug.

Which might not be out of the question.  I'd guess it's not uncommon
to only be interested in a small subset of the bug reports...  Hm...

So, how would this work?

You'd specify an nnbugzilla server with a handy command that says
which Bugzilla to use, and what components you want (and perhaps the
rest of the query criteria).  Fetching new news from this server would
be one buglist.cgi call, and one show_bug.cgi call per bug in this
list.

Entering a group would show you the report and the responses, of
course.

I think it's workable...

Then there's responding/changing state/adding Cc/and so on, which I
haven't looked into at all.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen




  reply	other threads:[~2006-04-13 11:45 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-13  8:47 Lars Magne Ingebrigtsen
2006-04-13 11:45 ` Lars Magne Ingebrigtsen [this message]
2006-04-13 12:43 ` Steve Youngs
2006-04-13 13:42   ` Lars Magne Ingebrigtsen
2006-04-13 14:20     ` Steve Youngs
2006-04-13 14:27       ` Lars Magne Ingebrigtsen
2006-04-13 14:58         ` Sebastian Freundt
2006-04-13 16:11           ` Lars Magne Ingebrigtsen
2006-04-13 14:28       ` Lars Magne Ingebrigtsen
2006-04-13 16:11       ` Romain Francoise
2006-04-13 16:25         ` Sebastian Freundt
2006-04-13 16:42           ` Lars Magne Ingebrigtsen
2006-04-13 16:44           ` Romain Francoise
2006-04-13 16:56     ` Lars Magne Ingebrigtsen
2006-05-17 19:36       ` Steinar Bang
2006-04-13 17:51     ` Nelson Ferreira
2006-04-14  6:14       ` Lars Magne Ingebrigtsen
2006-04-14  7:21         ` Nelson Ferreira
2006-04-14  7:41           ` Lars Magne Ingebrigtsen
2006-04-13 16:20 ` Wes Hardaker
2006-04-13 16:36   ` Lars Magne Ingebrigtsen
2006-04-13 17:02     ` Lars Magne Ingebrigtsen
2006-04-13 17:29       ` Steve Youngs
2006-04-13 17:36         ` Lars Magne Ingebrigtsen
2006-04-13 18:27           ` Steve Youngs
2006-04-13 18:52             ` Lars Magne Ingebrigtsen
2006-04-13 17:50       ` Lars Magne Ingebrigtsen
2006-04-13 18:24         ` Steve Youngs
2006-04-13 17:04     ` Steve Youngs
2006-04-13 21:50     ` Wes Hardaker
2006-04-13 18:44 ` Romain Francoise
2006-04-14  6:03   ` Lars Magne Ingebrigtsen
2006-04-14  6:23     ` Romain Francoise
2006-04-14  6:38       ` Lars Magne Ingebrigtsen
2006-05-17 19:42         ` 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=m3odz5pum1.fsf@quimbies.gnus.org \
    --to=larsi@gnus.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 NNTP newsgroup(s).