From: Michael Albinus <michael.albinus@gmx.de>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: bug#37854 <37854@debbugs.gnu.org>
Subject: bug#37854: 27.0.50; debbugs-gnu doesn't return date bugs were closed
Date: Tue, 22 Oct 2019 11:31:26 +0200 [thread overview]
Message-ID: <87tv81f7o1.fsf_-_@gmx.de> (raw)
In-Reply-To: <87y2xep3jm.fsf@gnus.org> (Lars Ingebrigtsen's message of "Mon, 21 Oct 2019 16:38:05 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
[continuing at <37854@debbugs.gnu.org>]
> But I wonder... fixed_date is one thing, but you can close a bug
> without marking it as fixed. Is there a separate date for the "close"
> action somewhere in the database?
>
> For instance,
>
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=18688
>
> was closed without being marked as "fixed".
Well, it looks like this close date is not an attribute of the bug, but
something the database keeps internal for countdown of the 28 days,
until the bug will be archived. Once archived, this information doesn't
seem to be available anymore.
Anyway, I've sent a request to <https://bugs.debian.org/942843>.
Best regards, Michael.
next prev parent reply other threads:[~2019-10-22 9:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-20 19:32 Bug statistics Eli Zaretskii
2019-10-20 20:15 ` Lars Ingebrigtsen
2019-10-21 6:17 ` Eli Zaretskii
2019-10-21 7:24 ` Michael Albinus
2019-10-21 11:05 ` Lars Ingebrigtsen
2019-10-21 11:20 ` Eli Zaretskii
2019-10-21 12:26 ` Stefan Monnier
2019-10-21 13:04 ` Lars Ingebrigtsen
2019-10-21 13:50 ` Michael Albinus
2019-10-21 13:54 ` Lars Ingebrigtsen
2019-10-21 14:19 ` Michael Albinus
2019-10-21 14:32 ` Michael Albinus
2019-10-21 17:12 ` Lars Ingebrigtsen
2019-10-21 14:38 ` Lars Ingebrigtsen
2019-10-22 9:31 ` Michael Albinus [this message]
2019-10-22 9:47 ` bug#37854: 27.0.50; debbugs-gnu doesn't return date bugs were closed Lars Ingebrigtsen
2019-10-24 8:20 ` Michael Albinus
2019-10-24 12:02 ` Lars Ingebrigtsen
2019-10-24 13:56 ` Michael Albinus
-- strict thread matches above, loose matches on Subject: below --
2019-10-21 17:12 Lars 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=87tv81f7o1.fsf_-_@gmx.de \
--to=michael.albinus@gmx.de \
--cc=37854@debbugs.gnu.org \
--cc=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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.