unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Eli Zaretskii <eliz@gnu.org>
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:36:55 +0000	[thread overview]
Message-ID: <87sf87flx4.fsf@localhost> (raw)
In-Reply-To: <83h6ono20s.fsf@gnu.org>

Eli Zaretskii <eliz@gnu.org> writes:

>> > Where (in what code) did you see this assumption?
>> 
>> `package--reload-previously-loaded'
>
> That probably needs to be fixed, but is package.el relevant to the
> issue discussed here?  Org is part of Emacs, so I don't expect
> package.el to be involved.

I do not think that this particular part of the code is responsible.
Just suspect that other places might have similar logic omission.
(Aside: that specific code _was_ a problem in Emacs 28, but I was unable
to create reproducer on master and did not report the problem. So, it
might be perfectly fine, or not. Someone more familiar with package.el
may need to take a look - I can report on emacs-devel or debbugs if you
think that it is worth it)

Also, I doubt that Org has anything to do with handling .el.gz files -
we do not fiddle with package loading, except in `org-assert-version'.
But there is nothing in there that seems relevant to the issue at hand.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>



  reply	other threads:[~2023-08-25 10:36 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
2023-08-25  7:42                           ` Ihor Radchenko
2023-08-25 10:21                             ` Eli Zaretskii
2023-08-25 10:36                               ` Ihor Radchenko [this message]
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

  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=87sf87flx4.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=acorallo@gnu.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=herbert@gojira.at \
    /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).