From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 25876-done@debbugs.gnu.org
Subject: bug#25876: 24.5; Misleading title for history menu from `Info-history'
Date: Sat, 04 Mar 2017 17:39:13 +0200 [thread overview]
Message-ID: <83o9xhjbku.fsf@gnu.org> (raw)
In-Reply-To: <0aec2440-cf06-461d-8d67-5eae9ce993f8@default> (message from Drew Adams on Sat, 25 Feb 2017 14:13:59 -0800 (PST))
> Date: Sat, 25 Feb 2017 14:13:59 -0800 (PST)
> From: Drew Adams <drew.adams@oracle.com>
>
> Please consider renaming the title to something that does not suggest
> that only the most recent elements of the history are included. Perhaps
> a name such as simply `Visited Nodes'.
Thanks, I made it say "History of Visited Nodes".
prev parent reply other threads:[~2017-03-04 15:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-25 22:13 bug#25876: 24.5; Misleading title for history menu from `Info-history' Drew Adams
2017-03-04 15:39 ` Eli Zaretskii [this message]
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=83o9xhjbku.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=25876-done@debbugs.gnu.org \
--cc=drew.adams@oracle.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).