From: Frank Schmitt <usereplyto@Frank-Schmitt.net>
Subject: Re: gnus bugs tracking
Date: Sat, 22 Mar 2003 18:49:21 +0100 [thread overview]
Message-ID: <ubs032swu.fsf@hschmi22.userfqdn.rz-online.de> (raw)
In-Reply-To: <ilubs03xu7l.fsf@latte.josefsson.org>
Simon Josefsson <jas@extundo.com> writes:
> Adding meta-data management to the current gnus.gnus-bug is one useful
> improvement I can see. Like, e.g., making it possible to enter the
> summary buffer and list all "open" bugs, and be able to "close" them
> somehow. I'm not sure how to best implement this though. With IMAP
> it would have been simple, by using "gnus-bug-open", "gnus-bug-fixed",
> "gnus-bug-wontfix" etc flags on the messages.
Well, you could do it the hard way by allowing the developers to
supersede the messages (only changing a X-bug-status header), but this
most probably won't work because of cancel-lock (well, we could tell
Gnus not to generate cancel-locks when creating a gnus-bug message).
The other option would be the following:
1) Every message created by M-x gnus-bug gets a special header like
X-Gnus-bug: report
2) If you e.g. fixed the bug you call a function gnus-bug-fixed with
point over the message which creates a mail buffer with
X-Gnus-bug: Report and the tag [fixed] in the subject
Other possible bug statuses would be
e.g. [fixed], [in-work], [postponed], [infos-missing], [no-bug]
3) If you want to see all open bugs, you look for every message with
X-Gnus-bug: Report
if it has a child with
X-Gnus-bug: fixed
This shouldn't be too hard to implement, but would probably mean two
runs over all headers (however, gnus-bug isn't very crowded, so this
should be not too slow).
--
One Ring to rule them all, One Ring to find them,
One Ring to bring them all and in the darkness bind them
In the Land of Mordor where the Shadows lie.
next prev parent reply other threads:[~2003-03-22 17:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-22 12:23 Alexander Kotelnikov
2003-03-22 12:42 ` Vasily Korytov
2003-03-22 13:14 ` Alexander Kotelnikov
2003-03-22 13:26 ` Frank Schmitt
2003-03-22 16:05 ` Simon Josefsson
2003-03-22 17:49 ` Frank Schmitt [this message]
2003-03-22 18:06 ` Alex Schroeder
2003-03-23 23:57 ` Alexander Kotelnikov
2003-03-26 12:18 ` Alexander Kotelnikov
2003-03-30 2:57 ` Lars Magne Ingebrigtsen
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=ubs032swu.fsf@hschmi22.userfqdn.rz-online.de \
--to=usereplyto@frank-schmitt.net \
--cc=replies@Frank-Schmitt.net \
/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).