From: Lars Ingebrigtsen <larsi@gnus.org>
To: Michael Albinus <michael.albinus@gmx.de>
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 14:02:34 +0200 [thread overview]
Message-ID: <871rv2fj1h.fsf@gnus.org> (raw)
In-Reply-To: <87mudqh7vi.fsf@gmx.de> (Michael Albinus's message of "Thu, 24 Oct 2019 10:20:49 +0200")
Michael Albinus <michael.albinus@gmx.de> writes:
> 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.
Ah, I see. Then building accurate statistics require downloading all
those (about 21K) URLs. I mean, that's totally doable, but... is that
something that the debbugs.gnu.org infrastructure team would frown upon?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-10-24 12:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <83lftf43hy.fsf@gnu.org>
[not found] ` <877e4zdvgx.fsf@gnus.org>
[not found] ` <83ftjm4o74.fsf@gnu.org>
[not found] ` <877e4ymugu.fsf@gmx.de>
[not found] ` <877e4yqmf9.fsf@gnus.org>
[not found] ` <878spegqbv.fsf@gmx.de>
[not found] ` <8736fmqk3x.fsf@gnus.org>
[not found] ` <874l02gp0q.fsf@gmx.de>
[not found] ` <87y2xep3jm.fsf@gnus.org>
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
2019-10-24 12:02 ` Lars Ingebrigtsen [this message]
2019-10-24 13:56 ` Michael Albinus
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
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=871rv2fj1h.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=37854@debbugs.gnu.org \
--cc=michael.albinus@gmx.de \
/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).