unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lynn Winebarger <owinebar@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Po Lu <luangruo@yahoo.com>, emacs-devel <emacs-devel@gnu.org>
Subject: Re: Docstring hack
Date: Sun, 31 Jul 2022 16:29:43 -0400	[thread overview]
Message-ID: <CAM=F=bDigTj_EGyvwoSfsx-swyUx9uRpoyzjaGyy9osJxn7+8Q@mail.gmail.com> (raw)
In-Reply-To: <83h72x4ekp.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1581 bytes --]

On Sun, Jul 31, 2022, 9:06 AM Eli Zaretskii <eliz@gnu.org> wrote:

> > From: Lynn Winebarger <owinebar@gmail.com>
> > Date: Sun, 31 Jul 2022 08:53:57 -0400
> > Cc: Po Lu <luangruo@yahoo.com>, emacs-devel <emacs-devel@gnu.org>
> >
> >  Does this mean that just resetting purify-flag is enough to avoid the
> >  problem?  If so, I think purify-flag is only meant for preloaded
> >  packages, and dumping Emacs with additional packages isn't supposed to
> >  set that flag.  Or maybe loadup.el should load an additional file
> >  (beyond site-load and site-init), after it resets purify-flag?
> >
> > I'm not sure why you'd not want to use the purify flag, since there are
> a lot of explicit calls to purecopy that
> > appear intended to take advantage of hash consing.  I don't know why
> that benefit should not apply to
> > libraries being preloaded by site-load and site-init.
>
> We will remove pure space at some not-too-distant future, which is a
> clear sign that it is not very important in the pdumper builds.  So
> investing time in something that works when purify-flag is off doesn't
> sound like a good investment to me.
>

I see your point.  I'm not that familiar with the policy on doing
maintenance releases on older versions (27 and 28 in particular).  Is pure
space elimination going to be incorporated in those as well?
Asking because AFAIK, 28.1 is only released as an rpm for "rolling release"
type distributions at this point, while (admittedly near EOL) installation
of RHEL 7.x still provide 24.3 as the "latest release" (for that antiquated
version).

Lynn

[-- Attachment #2: Type: text/html, Size: 2534 bytes --]

  reply	other threads:[~2022-07-31 20:29 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-30 12:14 Docstring hack Lynn Winebarger
2022-07-30 12:25 ` Po Lu
2022-07-30 12:50   ` Lynn Winebarger
2022-07-30 13:04     ` Lynn Winebarger
2022-07-30 13:32     ` Po Lu
2022-07-30 13:28 ` Eli Zaretskii
2022-07-30 13:36   ` Po Lu
2022-07-30 15:11     ` Eli Zaretskii
2022-07-30 15:38       ` Lynn Winebarger
2022-07-30 15:44         ` Eli Zaretskii
2022-07-30 16:32           ` Lynn Winebarger
2022-07-30 16:43             ` Eli Zaretskii
2022-07-31  2:17               ` Po Lu
2022-07-31  6:27                 ` Eli Zaretskii
2022-07-31  7:24                   ` Po Lu
2022-07-31  7:56                     ` Eli Zaretskii
2022-07-31  8:48                       ` Po Lu
2022-07-31  9:14                         ` Lars Ingebrigtsen
2022-07-31 22:31                           ` Stefan Monnier
2022-08-01 10:38                             ` Lars Ingebrigtsen
2022-08-04  4:12                         ` Lynn Winebarger
2022-07-31 12:53                       ` Lynn Winebarger
2022-07-31 13:05                         ` Eli Zaretskii
2022-07-31 20:29                           ` Lynn Winebarger [this message]
2022-08-01  1:05                             ` Po Lu
2022-08-01 11:07                             ` Eli Zaretskii
2022-07-31  8:03                   ` Stefan Monnier
2022-07-31 12:43                     ` Lynn Winebarger
2022-07-31 21:32                       ` Stefan Monnier
2022-08-02 16:55                         ` Lynn Winebarger
2022-07-31 11:57               ` Lynn Winebarger
2022-07-31  0:52       ` Po Lu
2022-07-31  7:52     ` Stefan Monnier

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='CAM=F=bDigTj_EGyvwoSfsx-swyUx9uRpoyzjaGyy9osJxn7+8Q@mail.gmail.com' \
    --to=owinebar@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=luangruo@yahoo.com \
    /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).