unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: emacs-devel@gnu.org
Subject: No README at someGNU mirrors
Date: Sat, 4 Mar 2017 16:17:34 -0800 (PST)	[thread overview]
Message-ID: <5ddfdccc-fcd1-4b9c-9249-486987dfd664@default> (raw)

At the GNU Emacs download page,
https://www.gnu.org/software/emacs/download.html, there is
a link, http://ftp.gnu.org/gnu/emacs/windows/, for downloading
GNU Emacs from the main site.  No problem with that.

There is another link, http://ftpmirror.gnu.org/emacs/windows,
which takes you to one of the mirror sites for downloading -
presumably a different mirror each time you follow the link.

Some of those mirror sites do not have the README file.
They have only the .zip's and .zip.sig's.

Without the README file you won't see this info, in particular:

  There are two binary distributions named
  emacs-n-x86_64-w64-mingw32.zip and
  emacs-n-i686-w64-mingw32.zip. These are for 64-bit and 32-bit
  machines respectively.

So you won't know which link to use.  The zip-file names
do not obviously tell you which is 64-bit and which is 32-bit.

Sure, many people will know what x86 vs i686 means.
And anyone can google "x86 vs i686", to find out, if
they don't know.  Still, some people will not know and
may not find out.

This is not as helpful for users as it should be.  Dunno
what the solution is.  Maybe a better naming scheme?
There are occurrences of "64" in both names, which can
add to the confusion.

Yes, it's clear enough if you have the README, and the
dates in the names etc. are clear enough.  But the 32-bit
vs 64-bit distinction is not very clear from just the zip
names.



                 reply	other threads:[~2017-03-05  0:17 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=5ddfdccc-fcd1-4b9c-9249-486987dfd664@default \
    --to=drew.adams@oracle.com \
    --cc=emacs-devel@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.
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).