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: Thu, 24 Oct 2019 10:20:49 +0200 [thread overview]
Message-ID: <87mudqh7vi.fsf@gmx.de> (raw)
In-Reply-To: <87k18xnmbv.fsf@gnus.org> (Lars Ingebrigtsen's message of "Tue, 22 Oct 2019 11:47:32 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
Hi Lars,
> Would it be possible to include the entire change history in the SOAP
> data? That is, the timestamps when tags/severities are added/removed?
> That is, is there a "log" of changes applied to a bug that can be
> output? If there was, that'd also fix the "closed" date handling
> problem.
Such history cannot be retrieved from the database I fear. So it cannot
be provided by the SOAP interface.
What you see in the bug reports logs web pages are all the messages,
received for a given bug. They are not downloaded by SOAP, but by their
URL like <https://debbugs.gnu.org/cgi/bugreport.cgi?mboxstat=yes;bug=37818>.
This is the counterpart to what is shown via
<https://debbugs.gnu.org/cgi/bugreport.cgi?bug=37818>.
All messages "bug marked as fixed in version 27.1, ...", as seen in that
example at the bottom, are control messages. One could extend the
"...bugreport.cgi?mboxstat=yes..." URL by another attribute
"mboxcontrol=yes" to download only control messages. They can be
identified by a "X-Debbugs-Envelope-To: control" header in the
messages. But this would miss the requests embedded directly in
messages, as seen in
<https://debbugs.gnu.org/cgi/bugreport.cgi?bug=37818#32>, for example.
Best regards, Michael.
next prev parent reply other threads:[~2019-10-24 8:20 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 ` bug#37854: 27.0.50; debbugs-gnu doesn't return date bugs were closed Michael Albinus
2019-10-22 9:47 ` Lars Ingebrigtsen
2019-10-24 8:20 ` Michael Albinus [this message]
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=87mudqh7vi.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.