From: Kaushal Modi <kaushal.modi@gmail.com>
To: Stefan Merten <stefan@merten-home.de>, Eli Zaretskii <eliz@gnu.org>
Cc: rgm@gnu.org, emacs-devel@gnu.org
Subject: Re: Emacs versions for rst.el
Date: Sat, 14 Jan 2017 18:14:57 +0000 [thread overview]
Message-ID: <CAFyQvY1_tO9Wonz9+CauF8F6p8AMFxL2EwhMK1HDG+r-tdNnFA@mail.gmail.com> (raw)
In-Reply-To: <5226.1484417032@eskebo.fritz.box>
[-- Attachment #1: Type: text/plain, Size: 787 bytes --]
You need to git clone the master branch, build emacs and do M-x
emacs-version in that.
On Sat, Jan 14, 2017, 1:04 PM Stefan Merten <stefan@merten-home.de> wrote:
> Hi all!
>
> 18 minutes ago Eli Zaretskii wrote:
> >> > The Emacs version number tells you what to use.
> >>
> >> Where do I find it?
> >
> > M-x emacs-version RET
>
> Results in 24.5.1 for me :-) . According to your information the next
> version is then 24.6...
>
> Seriously: Can you *please* give me some *useful* information on how
> to determine the next Emacs release in the development tree? May be
> this can be obtained by some git command?
>
>
> Grüße
>
> Stefan
>
> --
Kaushal Modi
[-- Attachment #2: Type: text/html, Size: 1607 bytes --]
next prev parent reply other threads:[~2017-01-14 18:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-14 18:03 Emacs versions for rst.el Stefan Merten
2017-01-14 18:14 ` Kaushal Modi [this message]
2017-01-14 19:02 ` Stefan Monnier
2017-01-14 19:01 ` Glenn Morris
2017-01-14 20:08 ` Eli Zaretskii
[not found] <20170103221540.4171.87517@vcs.savannah.gnu.org>
[not found] ` <20170103221541.47B2D2201B8@vcs.savannah.gnu.org>
2017-01-04 18:30 ` master 9ed3685: Lots of refactorings and a few minor improvements Glenn Morris
2017-01-07 10:28 ` Emacs versions for rst.el (was: Re: master 9ed3685: Lots of refactorings and a few minor improvements.) Stefan Merten
2017-01-11 23:06 ` Emacs versions for rst.el Glenn Morris
2017-01-14 15:21 ` Stefan Merten
2017-01-14 17:40 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAFyQvY1_tO9Wonz9+CauF8F6p8AMFxL2EwhMK1HDG+r-tdNnFA@mail.gmail.com \
--to=kaushal.modi@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rgm@gnu.org \
--cc=stefan@merten-home.de \
/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.