unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 57911@debbugs.gnu.org,
	"Mattias Engdegård" <mattias.engdegard@gmail.com>,
	"Stefan Monnier" <monnier@iro.umontreal.ca>
Subject: bug#57911: Abolish max-specpdl-size
Date: Mon, 19 Sep 2022 20:25:12 +0200	[thread overview]
Message-ID: <87r107rzlj.fsf@gnus.org> (raw)
In-Reply-To: <87mtavi85k.fsf@gmx.de> (Michael Albinus's message of "Mon, 19 Sep 2022 19:30:31 +0200")

Michael Albinus <michael.albinus@gmx.de> writes:

> The load average is just 0.31, but I don't know how it was earlier
> today.

Here's a mail from emacs-diffs, which exhibits the same behaviour:

Original-Received: from localhost ([::1]:47358 helo=lists1p.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.90_1)
	(envelope-from <emacs-diffs-bounces+gnu-emacs-diffs=m.gmane-mx.org@gnu.org>)
	id 1oaKza-0001VF-MR
	for gnu-emacs-diffs@m.gmane-mx.org; Mon, 19 Sep 2022 13:55:38 -0400
Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:37560)
 by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.90_1) (envelope-from <mattiase@acm.org>) id 1oaKfd-0002t6-5X
 for emacs-diffs@gnu.org; Mon, 19 Sep 2022 13:35:01 -0400

Received by eggs at 13:35:01 -0400, but not passed on until 13:55:38
-0400 -- 20 minutes later.

So it doesn't look like a debbugs.gnu.org thing, but a general gnu.org
mailing list thing?





  reply	other threads:[~2022-09-19 18:25 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-18 11:57 bug#57911: Abolish max-specpdl-size Mattias Engdegård
2022-09-19  7:10 ` Lars Ingebrigtsen
2022-09-19  9:35   ` Mattias Engdegård
2022-09-19 12:27     ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-19 15:35       ` Mattias Engdegård
2022-09-19 16:52         ` Michael Albinus
2022-09-19 17:09           ` Lars Ingebrigtsen
2022-09-19 17:30             ` Michael Albinus
2022-09-19 18:25               ` Lars Ingebrigtsen [this message]
2022-09-20 12:23                 ` Visuwesh
2022-09-20 15:52                   ` Eli Zaretskii
2022-09-20 16:23                     ` Visuwesh
2022-09-20 16:30                       ` Eli Zaretskii
2022-09-20 16:30                     ` Lars Ingebrigtsen
2022-09-20 16:36                       ` Eli Zaretskii
2022-09-20 16:48                         ` Lars Ingebrigtsen
2022-09-20 17:27                           ` Eli Zaretskii
2022-09-21 11:04                             ` Lars Ingebrigtsen
2022-09-20 21:51                     ` Gregory Heytings
2022-09-20 20:32                 ` Lars Ingebrigtsen
2022-09-21  0:02                   ` Gregory Heytings
2022-09-19 17:28           ` Mattias Engdegård
2022-09-19 12:40     ` Lars Ingebrigtsen
2022-09-19 13:54       ` Eli Zaretskii
2022-09-19 17:36         ` Mattias Engdegård

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=87r107rzlj.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=57911@debbugs.gnu.org \
    --cc=mattias.engdegard@gmail.com \
    --cc=michael.albinus@gmx.de \
    --cc=monnier@iro.umontreal.ca \
    /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).