From: Corwin Brust <corwin@bru.st>
To: Emacs developers <emacs-devel@gnu.org>,
"H. Dieter Wilhelm" <dieter@duenenhof-wilhelm.de>,
Eli Zaretskii <eliz@gnu.org>
Cc: Phillip Lord <phillip.lord@russet.org.uk>
Subject: Emacs 29.0.50 Snapshot binaries for WIndows
Date: Wed, 16 Feb 2022 21:37:48 -0600 [thread overview]
Message-ID: <CAJf-WoRAwsY4xj1YzjmmVOfYPk2+uoHu2ofX0dnGV8-70s8BeA@mail.gmail.com> (raw)
Hi All,
As much for my own testing as for yours, I have created a set of
binary "snapshot" releases of Emacs for Windows.
https://alpha.gnu.org/gnu/emacs/pretest/windows/?C=M;O=D
These reflect the master branch as of Feb 11th. Note, this took me
some time to accomplish. The dependencies were packaged the prior
weekend, but don't appear to have changed and should work fine. A zip
of the emacs sources used is also available as
emacs-29.0.50-snapshot-2022-02-11-src.zip
If you want these please grab them ASAP; I expect to move or remove
them fairly shortly. Apropos:
Eli, Dieter,
Do you agree we should continue to release Emacs snapshot builds for
Windows from master periodically? My leaning would be that we keep a
rolling "last few" available, building them once or twice a week on a
"best effort" basis.
Given you agree we should continue to publish snapshots at all, do you
have preferences as to where they are placed?
My leaning is to create a "snapshots" folder at the same level as the
emacs-28 directory, thus /gnu/emacs/pretest/windows/snapshots.
Another obvious candidate would be "emacs-29" but I 'm a little
hesitant it could cause confusion as to what release is imminent if we
have both emacs-28 and emacs-29 folders at the same level of the tree
while emacs-28 is still yet to be released.
In any case, I was hesitant to create any new folder/tree without
consultation but I did want to verify I can complete the process
"end-to-end".
I can easily move/remove these binaries, probably before work tomorrow
if you feel action is at all urgent. (I typically leave for the office
sometime around 8a America/Chicago.) If there is further cleanup to
attend to please feel free to let me know that also. I would plan to
archive anything else besides the just published snapshots. The
snapshots I would delete and then re-upload into the proper place (or
not).
Corwin
next reply other threads:[~2022-02-17 3:37 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-17 3:37 Corwin Brust [this message]
2022-02-17 6:38 ` Emacs 29.0.50 Snapshot binaries for WIndows Eli Zaretskii
2022-02-17 12:41 ` H. Dieter Wilhelm
2022-02-18 18:18 ` Phillip Lord
2022-02-19 4:57 ` Richard Stallman
2022-02-19 5:09 ` Po Lu
2022-02-19 8:40 ` Eli Zaretskii
2022-02-20 4:31 ` Richard Stallman
2022-02-20 4:34 ` Po Lu
2022-02-21 4:35 ` Richard Stallman
2022-02-21 4:57 ` Po Lu
2022-02-23 6:46 ` Richard Stallman
2022-02-21 5:18 ` Eli Zaretskii
2022-02-21 12:06 ` Tim Cross
2022-02-21 18:41 ` chad
2022-02-21 19:38 ` Eli Zaretskii
2022-02-22 1:08 ` Po Lu
2022-02-20 6:46 ` Eli Zaretskii
2022-02-21 4:35 ` Richard Stallman
2022-02-21 11:57 ` Dmitry Gutov
2022-02-24 22:41 ` phillip.lord
2022-02-19 11:14 ` Corwin Brust
2022-02-21 4:34 ` Richard Stallman
2022-02-23 14:33 ` Corwin Brust
2022-02-23 16:41 ` Stefan Monnier
2022-02-23 23:07 ` Corwin Brust
2022-02-24 6:55 ` Eli Zaretskii
2022-02-25 4:55 ` Corwin Brust
2022-02-25 11:28 ` Phillip Lord
2022-02-25 5:00 ` Richard Stallman
-- strict thread matches above, loose matches on Subject: below --
2023-02-01 7:36 c.buhtz
2023-02-01 20:24 ` Corwin Brust
2023-02-19 9:56 ` c.buhtz
2023-02-19 18:05 ` Corwin Brust
2023-02-24 5:33 ` Troy Brown
2023-02-24 6:43 ` c.buhtz
2023-02-24 8:22 ` Eli Zaretskii
2023-02-24 8:47 ` c.buhtz
2023-02-24 11:40 ` Eli Zaretskii
2023-02-24 21:01 ` c.buhtz
2023-02-24 21:17 ` Eli Zaretskii
2023-02-24 21:42 ` c.buhtz
2023-02-25 9:53 ` Eli Zaretskii
2023-02-26 15:17 ` c.buhtz
2023-02-26 15:48 ` Eli Zaretskii
2023-03-10 18:49 ` Corwin Brust
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=CAJf-WoRAwsY4xj1YzjmmVOfYPk2+uoHu2ofX0dnGV8-70s8BeA@mail.gmail.com \
--to=corwin@bru.st \
--cc=dieter@duenenhof-wilhelm.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--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).