unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: dieter@duenenhof-wilhelm.de, corwin@bru.st,
	phillip.lord@russet.org.uk, emacs-devel@gnu.org
Subject: Re: Emacs 29.0.50 Snapshot binaries for WIndows
Date: Sun, 20 Feb 2022 08:46:17 +0200	[thread overview]
Message-ID: <83fsoexcg6.fsf@gnu.org> (raw)
In-Reply-To: <E1nLdsP-00043Z-WC@fencepost.gnu.org> (message from Richard Stallman on Sat, 19 Feb 2022 23:31:13 -0500)

> From: Richard Stallman <rms@gnu.org>
> Cc: corwin@bru.st, emacs-devel@gnu.org, dieter@duenenhof-wilhelm.de,
> 	phillip.lord@russet.org.uk
> Date: Sat, 19 Feb 2022 23:31:13 -0500
> 
>   > >   > As much for my own testing as for yours, I have created a set of
>   > >   > binary "snapshot" releases of Emacs for Windows.
>   > > 
>   > > Do we have something lie this for GNU/Linux?
>   > > Or is there some reason why there is no need for them on GNU/Linux?
> 
>   > GNU/Linux users have the various distros that package Emacs binaries
>   > for them.  The volunteers who produce the MS-Windows binaries are in
>   > effect acting like such a distro for Windows users.
> 
> That's true, but (1) they do this for _releases_

That's not true, AFAIU: there are development snapshot releases as
well.

> and (2) it is not new.

Neither is the fact that we provide MS-Windows binaries.  Volunteers
were providing precompiled Emacs binaries for MS-Windows for many
years.  For example, in https://alpha.gnu.org/gnu/emacs/windows/ you
can see pretest binaries that go back as far as Emacs 25, and that's
after numerous cleanups.

> The "snapshot" releases are apparently something else.  How are they
> different from the Windows binaries volunteers have made in the past?

They aren't.  AFAIR, we had snapshots at least since Emacs 27 if not
earlier.



  parent reply	other threads:[~2022-02-20  6:46 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-17  3:37 Emacs 29.0.50 Snapshot binaries for WIndows Corwin Brust
2022-02-17  6:38 ` 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 [this message]
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=83fsoexcg6.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=corwin@bru.st \
    --cc=dieter@duenenhof-wilhelm.de \
    --cc=emacs-devel@gnu.org \
    --cc=phillip.lord@russet.org.uk \
    --cc=rms@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).