From: Michael Albinus <michael.albinus@gmx.de>
To: Stefan Kangas <stefan@marxist.se>
Cc: 39187@debbugs.gnu.org
Subject: bug#39187: Fwd: "Package refresh is already in progress, please wait..."
Date: Mon, 20 Jan 2020 14:52:24 +0100 [thread overview]
Message-ID: <87zheiw7zb.fsf@gmx.de> (raw)
In-Reply-To: <CADwFkm=BY+w3nqN64XTuxavrjenWb9jR6D-MNuNQMbj0aErH5Q@mail.gmail.com> (Stefan Kangas's message of "Mon, 20 Jan 2020 14:29:53 +0100")
Stefan Kangas <stefan@marxist.se> writes:
>> I've created bug#39200 for Emacs 27.1, and bug#39202 for Emacs
>> 28.1. I've also marked bug#39187 as blocking bug#39200.
>>
>> However, this will only work if this list of blocking bugs is maintained
>> by people.
>
> Thanks. I suggest to let emacs-devel know about this.
Will do. Just now I'm working on debbugs-gnu.el, in order to let it know
these special bugs. A new debbugs release shall appear soon.
OTOH, I don't know whether Eli has a policy when to declare a bug
blocking for a Emacs given release. We should avoid that everybody
declares her own pet bug as release-critical.
admin/release-process speaks only about the "how" of creating / handling
blocking bugs, not about "when".
> Best regards,
> Stefan Kangas
Best regards, Michael.
next prev parent reply other threads:[~2020-01-20 13:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CADwFkmmNJYecn62nN8rxfFqMD9dU75z_BfGebf89M4XmnmZZWA@mail.gmail.com>
2020-01-19 1:28 ` bug#39187: Fwd: "Package refresh is already in progress, please wait..." Jean-Christophe Helary
2020-01-19 1:55 ` Stefan Kangas
2020-01-19 9:09 ` Michael Albinus
2020-01-19 15:20 ` Eli Zaretskii
2020-01-20 12:36 ` Michael Albinus
2020-01-20 13:29 ` Stefan Kangas
2020-01-20 13:52 ` Michael Albinus [this message]
2020-01-23 18:18 ` Stefan Kangas
2020-02-09 20:33 ` Stefan Kangas
2020-02-09 21:41 ` Jean-Christophe Helary
2020-02-10 15:30 ` Stefan Kangas
2020-02-11 2:17 ` Jean-Christophe Helary
2020-02-11 5:55 ` Jean-Christophe Helary
2020-02-11 6:25 ` Stefan Kangas
2020-02-11 6:38 ` Jean-Christophe Helary
2020-03-22 11:40 ` Stefan Kangas
2020-04-08 1:22 ` Stefan Kangas
2020-04-08 1:50 ` Jean-Christophe Helary
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=87zheiw7zb.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=39187@debbugs.gnu.org \
--cc=stefan@marxist.se \
/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).