From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Drew Adams <drew.adams@oracle.com>
Cc: 27350@debbugs.gnu.org
Subject: bug#27350: 25.2; Make `inhibit-compacting-font-caches' customizable
Date: Tue, 13 Jun 2017 13:06:09 -0700 (PDT) [thread overview]
Message-ID: <6b87621e-b418-415a-b48a-3db2365ba66c@default> (raw)
In-Reply-To: <<834lvj4qva.fsf@gnu.org>>
> > I'm glad I brought it to your attention, in that case. ;-)
>
> But you didn't: the problem reported by the OP doesn't reproduce on my
> machine. That's why we need the people who actually have those
> problems to talk to us: we need to ask them to try several things in
> order to attempt to find the reason.
Which is why I pointed you to the OP, so you can ask the OP such things.
> > And you can also consider addressing the referenced "GitHub
> > discussion thread"
>
> I'm familiar with that thread, and the problem reported there is fixed
> in Emacs 26. So no, that doesn't help either.
>
> > Both of those references should presumably help you gather
> > info about "as many of these problems as possible".
>
> They don't. We need to have people with the problem report the
> details and be ready to work with us on them.
See above. Or maybe you have already contacted the OP and have
determined that the OP is not able or willing to give you the
details and work with you on them.
next parent reply other threads:[~2017-06-13 20:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<548efd73-7fb5-45ef-979d-59623d31df3b@default>
[not found] ` <<83fuf43p7m.fsf@gnu.org>
[not found] ` <<750f3b75-e3b0-4953-aae1-5635721f5d62@default>
[not found] ` <<834lvj4qva.fsf@gnu.org>
2017-06-13 20:06 ` Drew Adams [this message]
2017-06-13 14:33 bug#27350: 25.2; Make `inhibit-compacting-font-caches' customizable Drew Adams
2017-06-13 15:02 ` Eli Zaretskii
2017-06-13 17:02 ` Drew Adams
2017-06-13 19:41 ` 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=6b87621e-b418-415a-b48a-3db2365ba66c@default \
--to=drew.adams@oracle.com \
--cc=27350@debbugs.gnu.org \
--cc=eliz@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).