From: Eli Zaretskii <eliz@gnu.org>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: herbert@gojira.at, acorallo@gnu.org, emacs-devel@gnu.org
Subject: Re: master b5bbb29634e 1/5: Merge from origin/emacs-29
Date: Fri, 25 Aug 2023 10:18:43 +0300 [thread overview]
Message-ID: <83ledzoai4.fsf@gnu.org> (raw)
In-Reply-To: <87msyfipx5.fsf@localhost> (message from Ihor Radchenko on Fri, 25 Aug 2023 06:42:14 +0000)
> From: Ihor Radchenko <yantar92@posteo.net>
> Cc: "Herbert J. Skuhra" <herbert@gojira.at>, acorallo@gnu.org,
> emacs-devel@gnu.org
> Date: Fri, 25 Aug 2023 06:42:14 +0000
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > Then why would compressing a *.el file change the behavior?
>
> AFAIR, one of the ways .el.gz files got handled wrongly was an
> assumption in the code that file extension must be .elc/.el/.eln. But
> .el.gz files have .gz extension, which may be easily missed in the
> logic.
Where (in what code) did you see this assumption?
next prev parent reply other threads:[~2023-08-25 7:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <168941374579.21359.4311609468242997473@vcs2.savannah.gnu.org>
[not found] ` <20230715093546.7067CC06C72@vcs2.savannah.gnu.org>
2023-08-07 12:07 ` master b5bbb29634e 1/5: Merge from origin/emacs-29 Herbert J. Skuhra
2023-08-22 12:32 ` Herbert J. Skuhra
2023-08-24 6:02 ` Eli Zaretskii
2023-08-24 9:02 ` Herbert J. Skuhra
2023-08-24 9:15 ` Eli Zaretskii
2023-08-24 11:17 ` Ihor Radchenko
2023-08-24 14:10 ` Herbert J. Skuhra
2023-08-24 15:08 ` Eli Zaretskii
2023-08-24 16:29 ` Herbert J. Skuhra
2023-08-24 16:36 ` Eli Zaretskii
2023-08-25 6:42 ` Ihor Radchenko
2023-08-25 7:18 ` Eli Zaretskii [this message]
2023-08-25 7:42 ` Ihor Radchenko
2023-08-25 10:21 ` Eli Zaretskii
2023-08-25 10:36 ` Ihor Radchenko
2023-08-25 9:45 ` Andrea Corallo
2023-08-26 9:05 ` Herbert J. Skuhra
2023-08-26 9:41 ` Eli Zaretskii
2023-08-26 18:44 ` Herbert J. Skuhra
2024-04-16 22:42 ` Herbert J. Skuhra
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=83ledzoai4.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=acorallo@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=herbert@gojira.at \
--cc=yantar92@posteo.net \
/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.