From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Getting latest development version
Date: Sun, 27 Nov 2022 11:09:50 +0200 [thread overview]
Message-ID: <83zgccpxup.fsf@gnu.org> (raw)
In-Reply-To: <Y4Mh/4JmzNJfrLF6@protected.localdomain> (message from Jean Louis on Sun, 27 Nov 2022 11:38:23 +0300)
> Date: Sun, 27 Nov 2022 11:38:23 +0300
> From: Jean Louis <bugs@gnu.support>
> Cc: Eli Zaretskii <eliz@gnu.org>, help-gnu-emacs@gnu.org
>
> after that they click and redirect to mirror:
> https://gnuftp.uib.no/emacs/windows/
>
> and there is no way to see what to download exactly and what to do?
> They get this listing:
>
> Index of /emacs/windows
>
> Icon Name Last modified Size Description[PARENTDIR] Parent Directory -
> [DIR] emacs-22/ 2019-04-16 23:30 -
> [DIR] emacs-23/ 2019-04-16 22:50 -
> [DIR] emacs-24/ 2019-04-16 22:40 -
> [DIR] emacs-25/ 2019-04-16 22:35 -
> [DIR] emacs-26/ 2019-08-30 15:10 -
> [DIR] emacs-27/ 2021-03-31 18:49 -
> [DIR] emacs-28/ 2022-09-13 18:57 -
> [ ] libXpm-3.5.7-w32-src.zip 2008-03-26 13:16 79K
> [ ] libXpm-3.5.7-w32-src.zip.sig 2008-03-26 13:16 280
> [ ] libxpm-3.5.8-w32-src.zip 2010-04-10 02:12 1.4M
> [ ] libxpm-3.5.8-w32-src.zip.sig 2010-04-10 02:13 96
> [ ] xpm-nox-4.2.0-src.zip 2016-09-18 20:37 267K
> [ ] xpm-nox-4.2.0-src.zip.sig 2016-09-18 20:37 173
You have omitted the README file, which is shown the first in the list
above, before all the subdirectories, and has this text:
Each major version of Emacs is kept in its own subdirectory. Please
see the README files there for details of how to install and run
Emacs.
next prev parent reply other threads:[~2022-11-27 9:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-26 18:07 Getting latest development version Hans Lonsdale via Users list for the GNU Emacs text editor
2022-11-26 18:53 ` Emanuel Berg
2022-11-26 18:59 ` Eli Zaretskii
2022-11-26 19:06 ` Hans Lonsdale
2022-11-27 8:13 ` Eli Zaretskii
2022-11-27 8:38 ` Jean Louis
2022-11-27 9:09 ` Eli Zaretskii [this message]
2022-11-26 19:10 ` Jean Louis
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=83zgccpxup.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@gnu.org \
/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.
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).