From: Glenn Morris <rgm@gnu.org>
To: 18416@debbugs.gnu.org
Subject: bug#18416: EMACS_HEAPSIZE unexpanded (unused?)
Date: Fri, 05 Sep 2014 18:44:13 -0400 [thread overview]
Message-ID: <ndvbp13cxu.fsf@fencepost.gnu.org> (raw)
Package: emacs
Version: 24.4.50
Severity: minor
Current trunk on GNU/Linux, the generated src/Makefile contains an
unexpanded @EMACS_HEAPSIZE@. It's not used for anything, so it doesn't
really matter, but it seems like bad form. It would be better for it to
expand to the empty string, like it does in the emacs-24 branch.
Or perhaps it is now entirely unused and should just be removed?
BTW, there's no ChangeLog entry that says when EMACS_HEAPSIZE was
removed from configure.ac.
It seems it was
http://lists.gnu.org/archive/html/emacs-diffs/2014-05/msg00255.html
The ChangeLog entry should be improved.
next reply other threads:[~2014-09-05 22:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-05 22:44 Glenn Morris [this message]
2014-09-06 7:42 ` bug#18416: EMACS_HEAPSIZE unexpanded (unused?) Eli Zaretskii
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=ndvbp13cxu.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=18416@debbugs.gnu.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 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).