From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Gnus interface to Bugzilla?
Date: Fri, 14 Apr 2006 08:14:05 +0200 [thread overview]
Message-ID: <m3bqv4fzv6.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <m3y7y9gy95.fsf@tuxie.homelinux.net>
Nelson Ferreira <nelson.ferreira@ieee.org> writes:
> Why not 'overload' the concept of digest, i.e. treat the bug as a
> digest and C-d would give you the replies there? If message-ids are
> generated the read messages should still be marked as such right ?
It wouldn't tell me when new comments have been made.
Let's assume that nntp.cgi has been written, so that nnbugzilla can
get data out at a sensible speed.
One-group-per-search/product/category/whatever:
The user would have a command in the group buffer to create the group,
which would prompt for URL, category, etc, and then create the group
based on those criteria.
`M-g' on the group would issue one nntp.cgi call to get the bugs and
how many comments there have been made. nnbugzilla would maintain a
`(bug# comment# article-number)' triplet in a local file to be able to
map article numbers to bug/comments.
Say there has been one new comment made to a bug. `M-g' will report
one new article. Entering the group with `RET' does one show_bug.cgi
call (because of the mapping it knows which bug the user wants to
see), and displays the single comment.
Hitting `^' will go to the previous comment without any http traffic,
because Gnus will already have all the headers for this bug, and
threading works. `A T' will show all the comments in the bug.
If a bug disappears from the group, nnbugzilla removes all the
mappings for that bug. Or perhaps using an expiry scheme -- dead bugs
that are older than a month are removed.
Neat, huh?
The only problem is that the only way to display all open bug reports
in the category is to `C-u RET' the group, and display all the threads
to all the bugs. Which means issuing one show_bug.cgi per bug. So
just getting displaying what bugs are active would be s.l.o.w.
I think one-group-per-category just can't be made workable because of
this last problem.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2006-04-14 6:14 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 [this message]
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=m3bqv4fzv6.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).