From: Drew Adams <drew.adams@oracle.com>
To: phillip.lord@russet.org.uk, Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: RE: Windows Snapshots
Date: Mon, 4 Dec 2017 07:00:29 -0800 (PST) [thread overview]
Message-ID: <4760ab64-cfc1-43e1-ab92-bf876781e235@default> (raw)
In-Reply-To: <87o9nen1oe.fsf@russet.org.uk>
> Currently, the situation is made more complex by there being two
> architectures (32/64 bit) and three choices of download (with deps,
> without, installer). That's a lot of files to choose from. Not so much
> of a problem for the snapshots, but for a full release, I think it is.
Maybe put those 6 choices in 6 subdirs? Or 4 subdirs, or 2?
Or use file names that make the choices clearer?
Separate subdirs might be clearer, I think. And that could
let the file names, as well as the subdir names, be clearer.
(And each subdir could even have a small README that describes
the contents in plain English.)
Anyway, it's a good idea to pose the question - how best
to organize and present the choices to users. You might
get some good suggestions that will help.
(And thanks again for the builds.)
next prev parent reply other threads:[~2017-12-04 15:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-01 15:42 Windows Snapshots Phillip Lord
2017-12-01 16:03 ` Drew Adams
2017-12-01 17:56 ` Phillip Lord
2017-12-01 18:20 ` Drew Adams
2017-12-01 19:03 ` Phillip Lord
2017-12-01 19:20 ` Drew Adams
2017-12-03 0:07 ` Stefan Monnier
2017-12-04 12:00 ` Phillip Lord
2017-12-04 12:16 ` Nicolas Petton
2017-12-04 14:36 ` Phillip Lord
2017-12-04 15:02 ` Drew Adams
2017-12-04 15:00 ` Drew Adams [this message]
2017-12-05 10:22 ` Phillip Lord
2017-12-05 17:22 ` Sivaram Neelakantan
2017-12-09 11:22 ` Phillip Lord
-- strict thread matches above, loose matches on Subject: below --
2019-09-20 14:36 Phillip Lord
2019-10-24 16:36 ` Drew Adams
2019-11-11 17:27 ` Phillip Lord
2019-11-11 17:48 ` Drew Adams
2019-11-11 23:37 ` 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=4760ab64-cfc1-43e1-ab92-bf876781e235@default \
--to=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=phillip.lord@russet.org.uk \
/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).