From: Xue Fuqiao <xfq.free@gmail.com>
To: Nicolas Petton <nicolas@petton.fr>
Cc: Emacs-devel <emacs-devel@gnu.org>
Subject: Re: [emacs-announce] Emacs pretest 25.0.92
Date: Thu, 3 Mar 2016 07:00:04 +0800 [thread overview]
Message-ID: <CAAF+z6GzfC9AgA2KTH6Abszt8rQcp8iPSvrosLhV5umda7sAnw@mail.gmail.com> (raw)
In-Reply-To: <8737s8okj2.fsf@petton.fr>
On Thu, Mar 3, 2016 at 1:29 AM, Nicolas Petton <nicolas@petton.fr> wrote:
> Hi!
Hi Nicolas,
> The second pretest for what will be the 25.1 release of Emacs
> (the extensible text editor) is available at
>
> ftp://alpha.gnu.org/gnu/emacs/pretest/emacs-25.0.92.tar.xz
Thanks you!
I might be missing something, but it seems that 25.0.92 is the third
pretest (after 25.0.90 and 25.0.91), not the second one.
prev parent reply other threads:[~2016-03-02 23:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-02 17:29 [emacs-announce] Emacs pretest 25.0.92 Nicolas Petton
2016-03-02 23:00 ` Xue Fuqiao [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=CAAF+z6GzfC9AgA2KTH6Abszt8rQcp8iPSvrosLhV5umda7sAnw@mail.gmail.com \
--to=xfq.free@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=nicolas@petton.fr \
/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).