[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

debbugs-gnu-bugs shows unanswered bugs as handled

From: Tino Calancha
Subject: debbugs-gnu-bugs shows unanswered bugs as handled
Date: Sat, 4 Jun 2016 13:10:22 +0900 (JST)
User-agent: Alpine 2.20 (LRH 67 2015-01-07)

My version of debbugs is: 0.9.5


debbugs-gnu-bugs may show a bug with face debbugs-gnu-handled
even though such bug has not being answered yet.

Current implementation assumes a bug as new (not answered yet)
whenever attributes 'date and 'log_modified satisfies
predicate '=.

But for some new bugs 'date and 'log_modified may differ in 1 second.
For instance, the bugs:

The patch (see below) solve this issue relaxing the condition to
'log_modified - 'date < 3.


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.

For instance, let's suppose one user, FOO, send a bug report; some minutes
later, FOO send another e-mail (to same bug) adding extra information.

Current implementation shows that bug with face 'debbugs-gnu-handled.

That may cause the Emacs maintainers to think that someone is already
taking care on that issue.
It would be better if such bugs would not get 'debbugs-gnu-handled
face until some Emacs maintainer have already answered it.

Examples of this are:

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?

The value of this attribute could be defined as:
(length (delete-dups (from-list)))

where from-list is a list with the FROM field of all the e-mails
on that bug.

Then, `debbugs-get-status' would have such attribute set to 1 by
default; once the bug receive an answer from a different e-mail than
the OP then 'ncommunicators' would change to 2, and so on.


--- /tmp/ediff2583b8i   2016-06-04 12:39:37.169388859 +0900
+++ /home/calancha/.emacs.d/elpa/debbugs-0.9.5/debbugs-gnu.el   2016-06-03 
19:40:12.644524320 +0900
@@ -668,8 +668,8 @@
               ((member "pending" (cdr (assq 'keywords status)))
-              ((< (abs (- (cdr (assq 'date status))
-                       (cdr (assq 'log_modified status)))) 3)
+              ((= (cdr (assq 'date status))
+                  (cdr (assq 'log_modified status)))
               ((< (- (float-time)
                      (cdr (assq 'log_modified status)))

reply via email to

[Prev in Thread] Current Thread [Next in Thread]