From: Alex <agrambot@gmail.com>
To: npostavs@users.sourceforge.net
Cc: 27890@debbugs.gnu.org
Subject: bug#27890: 26.0.50; describe-font does not use Help buffer history
Date: Mon, 07 Aug 2017 15:19:45 -0600 [thread overview]
Message-ID: <878tivm5xq.fsf@lylat> (raw)
In-Reply-To: <8737946hwz.fsf@users.sourceforge.net> (npostavs's message of "Sun, 06 Aug 2017 07:43:08 -0400")
npostavs@users.sourceforge.net writes:
> No, let's not get bogged down in micro-optimization and just go with
> what you had originally.
Sounds good. Would you please commit it for me at an appropriate time?
Thanks.
next prev parent reply other threads:[~2017-08-07 21:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-31 21:25 bug#27890: 26.0.50; describe-font does not use Help buffer history Alex
2017-08-05 23:05 ` Alex
2017-08-06 0:21 ` npostavs
2017-08-06 2:01 ` Alex
2017-08-06 3:24 ` Alex
2017-08-06 11:43 ` npostavs
2017-08-07 21:19 ` Alex [this message]
2017-08-08 23:58 ` npostavs
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=878tivm5xq.fsf@lylat \
--to=agrambot@gmail.com \
--cc=27890@debbugs.gnu.org \
--cc=npostavs@users.sourceforge.net \
/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).