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 20:52:52 +0200	[thread overview]
Message-ID: <m3slohfgu3.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <microsoft-free.87k69tjpqf.fsf@youngs.au.com>

Steve Youngs <steve@sxemacs.org> writes:

>   >> Subject: search product=gnus owner=larsi state=open|new
>
>   > You'd post a news article to the server to get the list of groups?
>   > That's not very traditional.  :-)
>
> You're still thinking group-per-bug... I'm in group-per-product mode. :-)

Well, list of group, or list of bugs.  Still not very traditional.

Here are my thoughts before turning in for the night:

1) nnbugzilla will have to be reasonable fast for it to be used

2) Gnus needs article number counts for nnbugzilla to be interesting
   to use (I want to see whether there has been new discussion of a
   bug or bugs I'm watching)

3) There are many, many different versions of bugzilla out there, and
   none of the ones I have seen have commands that give us 2).
   Issuing one http call for each bug report in the active list means
   that 1) is impossible

Therefore, the only solution is to add a new, server-side mechanism,
nntp.cgi, which will (basically) output an active file.  It'll list
bug number, product, and short description, as well as the number of
responses it has had.

And then Gnus can do the rest on the client side.

So to use nnbugzilla, you will have to be, or know, the bugzilla
admin.  I can't see any other way to make this work.  Which is a bit
of a disappointment, because it would be nice to just be able to point
Gnus at a random Bugzilla repository and have it work.

I may be overlooking something, though.  :-)

Sleep now.

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




  reply	other threads:[~2006-04-13 18:52 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 [this message]
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=m3slohfgu3.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).