From: Eli Zaretskii <eliz@gnu.org>
To: Gregory Heytings <gregory@heytings.org>
Cc: dima@secretsauce.net, 48342@debbugs.gnu.org, akrl@sdf.org
Subject: bug#48342: native-comp emacs gets into an infinite loop at startup if no .el files are available
Date: Tue, 11 May 2021 22:51:39 +0300 [thread overview]
Message-ID: <83eeed3v78.fsf@gnu.org> (raw)
In-Reply-To: <a8104bf9de202662a735@heytings.org> (message from Gregory Heytings on Tue, 11 May 2021 19:38:30 +0000)
> Date: Tue, 11 May 2021 19:38:30 +0000
> From: Gregory Heytings <gregory@heytings.org>
> cc: dima@secretsauce.net, 48342@debbugs.gnu.org, akrl@sdf.org
>
> > My concern is about users who still have Emacs before March 2005.
>
> I forgot to mention that snapshot.debian.org also contains a copy of all
> earlier stable releases of Debian since ~1995.
Imagine the plight of a user who needs to discover all these places
just to have the sources available.
next prev parent reply other threads:[~2021-05-11 19:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-11 7:47 bug#48342: native-comp emacs gets into an infinite loop at startup if no .el files are available Dima Kogan
2021-05-11 8:37 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-05-11 8:44 ` Dima Kogan
2021-05-11 12:33 ` Eli Zaretskii
2021-05-11 17:00 ` Gregory Heytings
2021-05-11 17:12 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-05-11 17:29 ` Dima Kogan
2021-05-11 17:43 ` Eli Zaretskii
2021-05-11 17:57 ` Dima Kogan
2021-05-11 18:57 ` Gregory Heytings
2021-05-11 19:11 ` Eli Zaretskii
2021-05-11 19:38 ` Gregory Heytings
2021-05-11 19:51 ` Eli Zaretskii [this message]
2021-05-11 19:59 ` Dima Kogan
2021-05-11 20:23 ` Eli Zaretskii
2021-05-11 20:00 ` Gregory Heytings
2021-05-11 20:04 ` Gregory Heytings
2021-05-11 17:45 ` Eli Zaretskii
2021-05-11 19:43 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-02 16:44 ` Lars Ingebrigtsen
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=83eeed3v78.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=48342@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=dima@secretsauce.net \
--cc=gregory@heytings.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.