From: Eli Zaretskii <eliz@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: larsi@gnus.org, 43268@debbugs.gnu.org, kevin.legouguec@gmail.com
Subject: bug#43268: Update Org for Emacs 27.2
Date: Mon, 14 Dec 2020 18:45:54 +0200 [thread overview]
Message-ID: <831rfscp4t.fsf@gnu.org> (raw)
In-Reply-To: <87tuso2xhj.fsf@gmx.de> (message from Michael Albinus on Mon, 14 Dec 2020 16:55:36 +0100)
> From: Michael Albinus <michael.albinus@gmx.de>
> Cc: kevin.legouguec@gmail.com, 43268@debbugs.gnu.org, larsi@gnus.org
> Date: Mon, 14 Dec 2020 16:55:36 +0100
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> Maybe we could improve debbugs-gnu-emacs-release-blocking-reports to
> >> show only the open bugs.
> >
> > It could be useful to have an indication that it's closed, but I
> > wouldn't remove them nor hide them.
>
> There is an indication. The list shows the "done" tag, and it has
> another face.
Then I don't think I see a problem, thanks.
next prev parent reply other threads:[~2020-12-14 16:45 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 [this message]
2020-12-14 15:47 ` Lars Ingebrigtsen
2020-12-14 15:56 ` Michael Albinus
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=831rfscp4t.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=43268@debbugs.gnu.org \
--cc=kevin.legouguec@gmail.com \
--cc=larsi@gnus.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 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.