unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Merten <stefan@merten-home.de>
Cc: rgm@gnu.org, emacs-devel@gnu.org
Subject: Re: Emacs versions for rst.el
Date: Sat, 14 Jan 2017 22:08:06 +0200	[thread overview]
Message-ID: <83ziit9zh5.fsf@gnu.org> (raw)
In-Reply-To: <5226.1484417032@eskebo.fritz.box> (message from Stefan Merten on Sat, 14 Jan 2017 19:03:52 +0100)

> From: Stefan Merten <stefan@merten-home.de>
> cc: rgm@gnu.org, emacs-devel@gnu.org
> Date: Sat, 14 Jan 2017 19:03:52 +0100
> 
> > 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?

Sorry, I couldn't imagine you were making changes to the code without
actually testing it with the current Emacs sources of the branch into
which you push the changes.  The above command needs to be run inside
Emacs that's built from the branch where you are pushing.



  parent reply	other threads:[~2017-01-14 20:08 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
2017-01-14 19:02   ` Stefan Monnier
2017-01-14 19:01 ` Glenn Morris
2017-01-14 20:08 ` Eli Zaretskii [this message]
     [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

  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=83ziit9zh5.fsf@gnu.org \
    --to=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 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).