From: Eli Zaretskii <eliz@gnu.org>
To: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
Cc: michael.albinus@gmx.de, 43268@debbugs.gnu.org
Subject: bug#43268: Update Org for Emacs 27.2
Date: Mon, 14 Dec 2020 17:27:48 +0200 [thread overview]
Message-ID: <83lfe0csqz.fsf@gnu.org> (raw)
In-Reply-To: <87h7opie5k.fsf@gmail.com> (message from Kévin Le Gouguec on Sun, 13 Dec 2020 22:34:15 +0100)
> From: Kévin Le Gouguec <kevin.legouguec@gmail.com>
> Cc: Eli Zaretskii <eliz@gnu.org>, 43268@debbugs.gnu.org
> Date: Sun, 13 Dec 2020 22:34:15 +0100
>
> Closing this bug seems to have removed it from the list shown at the top
> of https://debbugs.gnu.org/43018 ("Fixed blocked by"); however, it's
> still present on M-x debbugs-gnu-emacs-release-blocking-reports (like
> 42851).
>
> 1. Do we care?
Only if you look at the results of that command (I don't).
> 2. If so,
> a. should I tell debbugs to "unblock 43018 by 43268"?
That'd be incorrect, because the bug could be reopened.
> b. should we teach debbugs.el to ignore closed bugs when listing
> blockers?
Why bother?
next prev parent reply other threads:[~2020-12-14 15:27 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
2020-12-14 18:44 ` Michael Albinus
2020-12-14 15:27 ` Eli Zaretskii [this message]
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
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=83lfe0csqz.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=43268@debbugs.gnu.org \
--cc=kevin.legouguec@gmail.com \
--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).