From: Michael Albinus <michael.albinus@gmx.de>
To: Tino Calancha <tino.calancha@gmail.com>
Cc: larsi@gnus.org, emacs-devel@gnu.org
Subject: Re: debbugs-gnu-bugs shows unanswered bugs as handled
Date: Sat, 04 Jun 2016 10:25:16 +0200 [thread overview]
Message-ID: <87inxpjr83.fsf@gmx.de> (raw)
In-Reply-To: <alpine.LRH.2.20.1606041259510.8787@calancha-ilc.kek.jp> (Tino Calancha's message of "Sat, 4 Jun 2016 13:10:22 +0900 (JST)")
Tino Calancha <tino.calancha@gmail.com> writes:
Hi Tino,
> debbugs-gnu-bugs may show a bug with face debbugs-gnu-handled
> even though such bug has not being answered yet.
>
> The patch (see below) solve this issue relaxing the condition to
> 'log_modified - 'date < 3.
Thanks for this. I've committed it to the ELPA repo. There are some few
other points on my debbugs todo list; will fix them over the
weekend. After this, debbugs 0.9.6 will be released.
> Another issue with the predicate to assign face 'debbugs-gnu-new
> is that it may consider as answered a bug where only the OP sent info.
>
> I don't see easy way to solve this with current implementation.
>
> Could be added a new attribute 'ncommunicators' to the status of a bug?
That's not possible. `debbugs-get-status' retrieves all information via
the Debbugs SOAP interface which are available, see its docstring. You
could check the attributes also in the *Emacs Bugs* buffer, typing "d"
(à la "debug") over a bug. The only exception here is "cache_time", this
attribute is added by debbugs.el.
Extending the SOAP interface this way is out of our scope, I fear. And
it would also decrease the performance.
I will add a note to the User Guide about this deficiency.
> Tino
Best regards, Michael.
next prev parent reply other threads:[~2016-06-04 8:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-04 4:10 debbugs-gnu-bugs shows unanswered bugs as handled Tino Calancha
2016-06-04 8:25 ` Michael Albinus [this message]
2016-06-05 14:50 ` Tino Calancha
2016-06-05 15:29 ` Michael Albinus
2016-06-08 13:29 ` Tino Calancha
2016-06-11 17:56 ` Michael Albinus
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87inxpjr83.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=tino.calancha@gmail.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).