From: Alexander Kotelnikov <sacha@myxomop.com>
Subject: Re: gnus bugs tracking
Date: Wed, 26 Mar 2003 15:18:58 +0300 [thread overview]
Message-ID: <87d6kejp71.fsf@pale.sj.ru> (raw)
In-Reply-To: <ilubs03xu7l.fsf@latte.josefsson.org> (Simon Josefsson's message of "Sat, 22 Mar 2003 17:05:34 +0100")
>>>>> On Sat, 22 Mar 2003 17:05:34 +0100
>>>>> "SJ" == Simon Josefsson <jas@extundo.com> wrote:
SJ>
SJ> Alexander Kotelnikov <sacha@myxomop.com> writes:
>> Hi.
>>
>> Sometimes bugs reported to ding@gnus.org are forgotten without a fix.
>> It's a pity. And it is a trouble, since gnus does not have its own bug
>> tracking system.
>>
>> Any comments?
SJ>
SJ> Adding meta-data management to the current gnus.gnus-bug is one useful
SJ> improvement I can see. Like, e.g., making it possible to enter the
SJ> summary buffer and list all "open" bugs, and be able to "close" them
SJ> somehow. I'm not sure how to best implement this though. With IMAP
SJ> it would have been simple, by using "gnus-bug-open", "gnus-bug-fixed",
SJ> "gnus-bug-wontfix" etc flags on the messages.
BTW, there is no good way to perform searching on bugs.
Ad the thing I forgot to ask: is it ok to post bug reports directly to
gnus-bug?
--
Alexander Kotelnikov
Saint-Petersburg, Russia
next prev parent reply other threads:[~2003-03-26 12:18 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
2003-03-22 18:06 ` Alex Schroeder
2003-03-23 23:57 ` Alexander Kotelnikov
2003-03-26 12:18 ` Alexander Kotelnikov [this message]
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=87d6kejp71.fsf@pale.sj.ru \
--to=sacha@myxomop.com \
/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).