all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Corwin Brust <corwin@bru.st>
Cc: Eli Zaretskii <eliz@gnu.org>,  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, 06 May 2022 19:15:31 -0400	[thread overview]
Message-ID: <jwvh76245nf.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <CAJf-WoTwt-6s9rW96j6-TdAzY-Lu8pj7oq1hRgiSbuj8ahSXXg@mail.gmail.com> (Corwin Brust's message of "Fri, 6 May 2022 18:05:03 -0500")

Corwin Brust [2022-05-06 18:05:03] wrote:
> 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.

For me the point is much simpler, in that it avoids issues like caches
that are out of date [ And it simplifies questions about "did you
download before or after I pushed the new build"?  ]


        Stefan




  reply	other threads:[~2022-05-06 23:15 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
2022-05-06 23:15           ` Stefan Monnier [this message]
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=jwvh76245nf.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=corwin@bru.st \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --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.