From: Eli Zaretskii <eliz@gnu.org>
To: Glenn Morris <rgm@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: /srv/bzr/emacs/trunk r110582: Fix wording of error message in staticpro.
Date: Fri, 19 Oct 2012 08:38:04 +0200 [thread overview]
Message-ID: <83hapr0xwz.fsf@gnu.org> (raw)
In-Reply-To: <wh7gqntqdy.fsf@fencepost.gnu.org>
> From: Glenn Morris <rgm@gnu.org>
> Cc: emacs-devel@gnu.org
> Date: Thu, 18 Oct 2012 17:35:37 -0400
>
> Eli Zaretskii wrote:
>
> >> IMO, the second clause should be absent altogether, or say "please make
> >> a bug report". As with puresize, this is not something users should be
> >> changing.
> >
> > As long as we are bykeshedding, how about
> >
> > NSTATICS should be enlarged.
>
> I don't think I'm bikeshedding, I'm trying to discourage people from
> thinking that these parts are intended to be user-serviceable.
I don't see the connection. The issue here is that _maintainers_ of
Emacs who get the bug report will instantly know what to do instead of
running Emacs under a debugger or asking the OP to do so.
> This kind of thing
>
> http://lists.gnu.org/archive/html/emacs-devel/2012-10/msg00253.html
>
> Now that I have set extra pure size to an obscene amount I
> will never see the warning anymore.
>
> is bad (IMO).
I agree, but I don't see a relation.
next prev parent reply other threads:[~2012-10-19 6:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1TOvam-0004TF-2u@vcs.savannah.gnu.org>
[not found] ` <5080564C.5090309@dancol.org>
2012-10-18 20:39 ` /srv/bzr/emacs/trunk r110582: Fix wording of error message in staticpro Glenn Morris
2012-10-18 20:50 ` Eli Zaretskii
2012-10-18 21:35 ` Glenn Morris
2012-10-19 6:38 ` Eli Zaretskii [this message]
2012-10-19 17:41 ` Glenn Morris
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=83hapr0xwz.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rgm@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 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.