From: Paul Eggert <eggert@cs.ucla.edu>
To: Nicolas Petton <nicolas@petton.fr>, Emacs Devel <emacs-devel@gnu.org>
Subject: Re: Emacs pretest 26.1.91 is out
Date: Mon, 7 Jan 2019 17:25:12 -0800 [thread overview]
Message-ID: <f773dba8-4967-515a-bf40-68e9965b193e@cs.ucla.edu> (raw)
In-Reply-To: <87ftu430u6.fsf@petton.fr>
On 1/7/19 8:10 AM, Nicolas Petton wrote:
> The second pretest for what will be the 26.2 release of Emacs
> (the extensible text editor) is available at
>
> ftp://alpha.gnu.org/gnu/emacs/pretest/emacs-26.1.91.tar.xz
>
> You can get the PGP signature at
>
> ftp://alpha.gnu.org/gnu/emacs/pretest/emacs-26.1.91.tar.xz.sig
Thanks for doing that. In the future, would you please announce URLs
like the following instead?
https://alpha.gnu.org/gnu/emacs/pretest/emacs-26.1.91.tar.xz
Granted, if one checks the PGP signature then FTP will do, but lots of
people don't bother with checking signatures and HTTPS is more secure in
that situation. Thanks.
next prev parent reply other threads:[~2019-01-08 1:25 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-07 16:10 Emacs pretest 26.1.91 is out Nicolas Petton
2019-01-07 21:42 ` John Wiegley
2019-01-07 22:11 ` Glenn Morris
2019-01-07 23:03 ` Nicolas Petton
2019-01-08 3:35 ` Eli Zaretskii
2019-01-08 0:59 ` Paul Eggert
2019-01-11 1:03 ` Glenn Morris
2019-01-11 2:31 ` Paul Eggert
2019-01-16 10:30 ` what make-dist should include [was Re: Emacs pretest 26.1.91 is out] Glenn Morris
2019-01-17 5:42 ` Mike Kupfer
2019-01-17 21:44 ` Stefan Monnier
2019-01-18 0:18 ` Mike Kupfer
2019-01-18 3:01 ` Stefan Monnier
2019-01-20 1:08 ` Mike Kupfer
2019-01-20 14:42 ` Stefan Monnier
2019-01-18 8:38 ` Eli Zaretskii
2019-01-20 0:54 ` Mike Kupfer
2019-01-18 18:58 ` Glenn Morris
2019-01-22 21:58 ` Paul Eggert
2019-01-23 16:14 ` Eli Zaretskii
2019-01-23 17:52 ` Paul Eggert
2019-01-23 18:14 ` Eli Zaretskii
2019-01-08 1:25 ` Paul Eggert [this message]
2019-01-08 8:53 ` Emacs pretest 26.1.91 is out Nicolas Petton
2019-01-09 15:02 ` Phillip Lord
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=f773dba8-4967-515a-bf40-68e9965b193e@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--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).