From: Corwin Brust <corwin@bru.st>
To: Stefan Monnier <monnier@iro.umontreal.ca>, Eli Zaretskii <eliz@gnu.org>
Cc: Glenn Morris <rgm@gnu.org>,
Sivaram Neelakantan <nsivaram.net@gmail.com>,
Emacs developers <emacs-devel@gnu.org>
Subject: Re: windows Emacs-version issue
Date: Fri, 6 May 2022 18:05:03 -0500 [thread overview]
Message-ID: <CAJf-WoTwt-6s9rW96j6-TdAzY-Lu8pj7oq1hRgiSbuj8ahSXXg@mail.gmail.com> (raw)
In-Reply-To: <jwv8rre5pec.fsf-monnier+emacs@gnu.org>
On Fri, May 6, 2022 at 4:24 PM Stefan Monnier <monnier@iro.umontreal.ca> wrote:
>
> How the new name is generated doesn't matter too much, so just try and
> find something that won't bring up too many questions or confusion.
> I've often seen "-N" being used for that, so it could be
> `emacs-28.1-2.zip` or `emacs-28.1-build2.zip`.
I'd object to adding numbers without explanation to the end of the
file names but I could live with adding a -buildNN suffix. TBH, I
really don't see the point. Each version of a release file is
properly described as "the given version of Emacs without any build
issues we know of that aren't open in Debbugs". But I understand that
view may be myopic. I could live with this.
Eli,
Do you agree with the proposal to rename Window binary releases as described?
next prev parent reply other threads:[~2022-05-06 23:05 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
2022-05-06 20:56 ` Corwin Brust
2022-05-06 21:24 ` Stefan Monnier
2022-05-06 23:05 ` Corwin Brust [this message]
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=CAJf-WoTwt-6s9rW96j6-TdAzY-Lu8pj7oq1hRgiSbuj8ahSXXg@mail.gmail.com \
--to=corwin@bru.st \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=nsivaram.net@gmail.com \
--cc=rgm@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 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.