all messages for Emacs-related lists mirrored at yhetil.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 19:40:53 +0200	[thread overview]
Message-ID: <8360lhbkuy.fsf@gnu.org> (raw)
In-Reply-To: <4207.1484407312@eskebo> (message from Stefan Merten on Sat, 14 Jan 2017 16:21:52 +0100)

> From: Stefan Merten <stefan@merten-home.de>
> Comments: In-reply-to Glenn Morris <rgm@gnu.org>
> 	message dated "Wed, 11 Jan 2017 18:06:23 -0500."
> Date: Sat, 14 Jan 2017 16:21:52 +0100
> Cc: emacs-devel@gnu.org
> 
> > The Emacs version number tells you what to use.
> 
> Where do I find it?

M-x emacs-version RET

> > Eg current version of master = 26.0.50 -> next release from master will
> > be 26.1. So you should have used 26.1 in place of 26.2. No need to
> > guess, or to follow development lists.
> 
> Can you give me a quick command to find this out? Is it documented
> somewhere?

See above.  Yes, in the Emacs user manual, node "Understanding Bug
Reporting".



  reply	other threads:[~2017-01-14 17:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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 [this message]
2017-01-14 18:03 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

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=8360lhbkuy.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 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.