From: Eli Zaretskii <eliz@gnu.org>
To: Lynn Winebarger <owinebar@gmail.com>
Cc: luangruo@yahoo.com, emacs-devel@gnu.org
Subject: Re: Docstring hack
Date: Mon, 01 Aug 2022 14:07:15 +0300 [thread overview]
Message-ID: <835yjc43z0.fsf@gnu.org> (raw)
In-Reply-To: <CAM=F=bDigTj_EGyvwoSfsx-swyUx9uRpoyzjaGyy9osJxn7+8Q@mail.gmail.com> (message from Lynn Winebarger on Sun, 31 Jul 2022 16:29:43 -0400)
> From: Lynn Winebarger <owinebar@gmail.com>
> Date: Sun, 31 Jul 2022 16:29:43 -0400
> Cc: Po Lu <luangruo@yahoo.com>, emacs-devel <emacs-devel@gnu.org>
>
> 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?
No, we are not going to backport such significant changes.
next prev parent reply other threads:[~2022-08-01 11:07 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
2022-08-01 1:05 ` Po Lu
2022-08-01 11:07 ` Eli Zaretskii [this message]
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=835yjc43z0.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.com \
--cc=owinebar@gmail.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).