From: Michael Albinus <michael.albinus@gmx.de>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 43268@debbugs.gnu.org, "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
Subject: bug#43268: Update Org for Emacs 27.2
Date: Mon, 14 Dec 2020 16:56:43 +0100 [thread overview]
Message-ID: <87pn3c2xfo.fsf@gmx.de> (raw)
In-Reply-To: <87wnxk1jb5.fsf@gnus.org> (Lars Ingebrigtsen's message of "Mon, 14 Dec 2020 16:47:10 +0100")
Lars Ingebrigtsen <larsi@gnus.org> writes:
>> Maybe we could improve debbugs-gnu-emacs-release-blocking-reports to
>> show only the open bugs.
>>
>> Eli? Lars?
>
> I think I vaguely prefer having it list all the (unarchived) blocker
> bugs? Then you can watch the number of closed blocker bugs grow, which
> seems satisfying. :-)
So I'll change nothing. Seeing archived bugs is even more satifying.
Best regards, Michael.
next prev parent reply other threads:[~2020-12-14 15:56 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-08 5:06 bug#43268: Update Org for Emacs 27.2 Kévin Le Gouguec
2020-09-08 14:17 ` Eli Zaretskii
2020-09-08 14:46 ` Michael Albinus
2020-09-08 14:58 ` Eli Zaretskii
2020-12-13 21:34 ` Kévin Le Gouguec
2020-12-14 7:50 ` Michael Albinus
2020-12-14 15:41 ` Eli Zaretskii
2020-12-14 15:55 ` Michael Albinus
2020-12-14 16:45 ` Eli Zaretskii
2020-12-14 15:47 ` Lars Ingebrigtsen
2020-12-14 15:56 ` Michael Albinus [this message]
2020-12-14 18:44 ` Michael Albinus
2020-12-14 15:27 ` Eli Zaretskii
2020-09-08 22:01 ` Kévin Le Gouguec
2020-11-23 20:09 ` Stefan Kangas
2020-11-26 16:41 ` Eli Zaretskii
2020-11-26 16:48 ` Bastien
2020-11-26 19:17 ` Eli Zaretskii
2020-11-26 22:49 ` Bastien
2020-12-02 15:10 ` Eli Zaretskii
2020-12-08 15:11 ` Eli Zaretskii
2020-12-08 15:35 ` Bastien
2020-12-08 17:01 ` Eli Zaretskii
2020-12-13 21:12 ` Kévin Le Gouguec
2020-11-26 21:41 ` Kévin Le Gouguec
2020-11-26 22:49 ` Bastien
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=87pn3c2xfo.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=43268@debbugs.gnu.org \
--cc=kevin.legouguec@gmail.com \
--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.