From: phillip.lord@russet.org.uk (Phillip Lord)
To: Drew Adams <drew.adams@oracle.com>
Cc: Emacs Devel <emacs-devel@gnu.org>,
Noam Postavsky <npostavs@users.sourceforge.net>
Subject: Re: [emacs-announce] Emacs pretest 26.0.90 is out
Date: Tue, 17 Oct 2017 15:53:38 +0100 [thread overview]
Message-ID: <87k1zt6d1p.fsf@russet.org.uk> (raw)
In-Reply-To: <14fb5a0b-30cb-4a04-8fef-24962cb6d811@default> (Drew Adams's message of "Tue, 17 Oct 2017 07:06:50 -0700 (PDT)")
Drew Adams <drew.adams@oracle.com> writes:
>> > What _are_ those *-deps zip files?
>> > What does "deps" stand for?
>>
>> Your questions are answered here:
>> https://urldefense.proofpoint.com/v2/url?u=https-
>> 3A__alpha.gnu.org_gnu_emacs_pretest_windows_README-2Demacs26-
>> 2Dpretests&d=DwIBaQ&c=RoP1YumCXCgaWHvlZYR8PQcxBKCX5YTpkKY057SbK10&r=qZLZo
>> sY6GBAaJtOG9v8QX7nD4BS9t9s5otgxC3d4IFU&m=id_9at6z1Pc2fkgBNw2Cix0Z8WJQiDBp
>> 1mIa-xBFENs&s=oEcXByM_Hjss9Nt7qtjlb6wOmCuCjW67KCThPjGZWbQ&e=
>
> Got it. And now they are (indirectly) answered in
> this announcement thread too. Thank you.
>
> (Except that "the dependencies" is defined nowhere.
> You have to guess what might be meant by that.)
Yes, this is true.
My plan for the next pre-test is to turn these around. So
"emacs-$version.zip" will contain all the dependencies while
"emacs-$version-no-deps.zip" will not. Then people who don't know what
to choose will get bells and whistles by default.
It would be quite nice to add a "runemacs.bat" file at top level also, I
think, but it's probably too late in the release cycle for this.
Phil
next prev parent reply other threads:[~2017-10-17 14:53 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-11 21:46 [emacs-announce] Emacs pretest 26.0.90 is out Nicolas Petton
2017-10-17 11:05 ` Phillip Lord
2017-10-17 13:40 ` Drew Adams
2017-10-17 13:44 ` Noam Postavsky
2017-10-17 14:06 ` Drew Adams
2017-10-17 14:53 ` Phillip Lord [this message]
2017-10-17 18:14 ` Richard Copley
2017-10-25 20:41 ` Stephen Leake
2017-10-25 20:46 ` Noam Postavsky
2017-10-25 20:57 ` Stefan Monnier
2017-10-26 20:33 ` Stephen Leake
2017-11-03 9:53 ` Eli Zaretskii
2017-11-03 17:09 ` Stephen Leake
2017-11-03 18:48 ` Phillip Lord
2017-11-03 19:46 ` INSTALL.W64 Stephen Leake
2017-11-03 20:18 ` INSTALL.W64 Eli Zaretskii
2017-11-03 22:55 ` INSTALL.W64 Fabrice Popineau
2017-11-04 9:02 ` INSTALL.W64 Michael Albinus
2017-11-04 10:58 ` INSTALL.W64 Fabrice Popineau
2017-11-04 12:08 ` INSTALL.W64 Michael Albinus
2017-11-04 12:17 ` INSTALL.W64 Eli Zaretskii
2017-11-04 12:29 ` INSTALL.W64 Fabrice Popineau
2017-11-04 13:14 ` INSTALL.W64 Eli Zaretskii
2017-11-04 13:26 ` INSTALL.W64 Michael Albinus
2017-11-04 13:39 ` INSTALL.W64 Eli Zaretskii
2017-11-03 21:15 ` INSTALL.W64 Phillip Lord
2017-11-04 7:52 ` INSTALL.W64 Eli Zaretskii
2017-11-03 20:09 ` [emacs-announce] Emacs pretest 26.0.90 is out Eli Zaretskii
2017-11-03 21:17 ` Phillip Lord
2017-11-04 7:54 ` Eli Zaretskii
2017-10-26 6:32 ` Jeremie Courreges-Anglas
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=87k1zt6d1p.fsf@russet.org.uk \
--to=phillip.lord@russet.org.uk \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=npostavs@users.sourceforge.net \
/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).