all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Corwin Brust <corwin@bru.st>
Cc: Sivaram Neelakantan <nsivaram.net@gmail.com>,
	Emacs developers <emacs-devel@gnu.org>
Subject: Re: windows Emacs-version issue
Date: Fri, 06 May 2022 16:48:25 -0400	[thread overview]
Message-ID: <bv35hm75gm.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <CAJf-WoR75pBFmG1U=RJgXaFbOfqXM-OJ1wMBPf7OQ96QG2ST7w@mail.gmail.com> (Corwin Brust's message of "Fri, 6 May 2022 10:40:22 -0500")


I think the point being made here is that binary releases, like source
releases, should be version tagged, and once uploaded, should not be
replaced in-situ (because that eg breaks checksumming, and is generally
confusing). IMO the binaries uploaded to ftp.gnu.org/gnu/emacs/windows
should have some extra version string added to the filename, and it
should be incremented if a new build is uploaded. Eg "emacs-28.1-version1.zip".

Ref https://lists.gnu.org/r/emacs-devel/2022-04/msg01108.html
for replacement of the original Windows files.



  reply	other threads:[~2022-05-06 20:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-05 14:26 windows Emacs-version issue Sivaram Neelakantan
2022-05-06 15:40 ` Corwin Brust
2022-05-06 20:48   ` Glenn Morris [this message]
2022-05-06 20:56     ` Corwin Brust
2022-05-06 21:24       ` Stefan Monnier
2022-05-06 23:05         ` Corwin Brust
2022-05-06 23:15           ` Stefan Monnier
2022-05-07  1:42             ` Corwin Brust
2022-05-07 13:18               ` Stefan Monnier
2022-05-07  5:43       ` Eli Zaretskii

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bv35hm75gm.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=corwin@bru.st \
    --cc=emacs-devel@gnu.org \
    --cc=nsivaram.net@gmail.com \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.