From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Gnus interface to Bugzilla?
Date: Fri, 14 Apr 2006 08:38:07 +0200 [thread overview]
Message-ID: <m3irpcd5m8.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <87bqv47k0g.fsf@pacem.orebokech.com>
Romain Francoise <romain@orebokech.com> writes:
> How current are your sources? I'm pretty sure 2.20 has it.
2.20.1... Ah, I just didn't grep deeply enough into the tree. Yes,
buglist.cgi has a ctype=rss format. And interestingly enough, it has
some useful data not found in the other formats. :-)
<entry>
<title>[Bug 119627] GridLayout - feedback does not allow dropping in all pla
ces</title>
<link rel="alternate" type="text/html"
href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=119627"/>
<id>https://bugs.eclipse.org/bugs/show_bug.cgi?id=119627</id>
<author>
<name>Joe Winchester</name>
</author>
<updated>2005-12-08T15:10:16Z</updated>
<summary type="html">
The interesting item here being <updated>. With this field,
nnbugzilla should be able to keep track of which bug reports have
been, er, updated, and issue a show_bug.cgi call for those that have
been updated.
No need for the proposed nntp.cgi program.
(Of course, the first time you use nnbugzilla, it will take quite a
long time, but each subsequent `g' will only issue one buglist.cgi
call. (Plus extra calls for each bug that has been updated, but
that'll happen quite rarely in comparison.))
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2006-04-14 6:38 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
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 [this message]
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=m3irpcd5m8.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).