From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: How to find when a feature was introduced
Date: Fri, 08 Jul 2016 09:43:00 +0300 [thread overview]
Message-ID: <831t34k4uj.fsf@gnu.org> (raw)
In-Reply-To: <dd89c256-33e9-4dbd-af47-5c72e0b7db7c@googlegroups.com> (message from Rusi on Thu, 7 Jul 2016 21:28:06 -0700 (PDT))
> Date: Thu, 7 Jul 2016 21:28:06 -0700 (PDT)
> From: Rusi <rustompmody@gmail.com>
>
> So now I need to tell my students gnu-apl-mode will not run in emacsen less than
> version X
>
> How to find out X?
First, try the NEWS method that someone else pointed to.
If that doesn't work, and the symbol is a defcustom, it should have a
:version tag (if it isn't, report that as a bug).
If that doesn't work either, or is inapplicable, the most elaborate
method that _always_ works is this:
. C-h f SOMETHING or C-h v SOMETHING
. note the place in the sources where SOMETHING is defined
. go to the nearest Emacs Git repository and use Git facilities to
find out the date on which the code was added
. consult etc/HISTORY to see which Emacs release the date
corresponds to
Notes:
(1) The Git facilities are "git annotate" and "git log -L".
(2) Due to branching before the release, a date that is before a
release doesn't necessarily mean the feature was in that release, you
will have to see when the release branch was cut; there should be a
Git tag at the branch point.
next prev parent reply other threads:[~2016-07-08 6:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-08 4:28 How to find when a feature was introduced Rusi
2016-07-08 4:41 ` Kaushal Modi
2016-07-08 4:53 ` Paul Rankin
2016-07-08 5:44 ` Drew Adams
2016-07-08 16:40 ` Drew Adams
2016-07-09 18:21 ` Kaushal Modi
[not found] ` <mailman.936.1468088520.26859.help-gnu-emacs@gnu.org>
2016-07-10 6:51 ` Rusi
2016-07-08 6:43 ` Eli Zaretskii [this message]
2016-07-08 16:33 ` Kaushal Modi
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=831t34k4uj.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@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.