From: Jim Porter <jporterbugs@gmail.com>
To: Corwin Brust <corwin@bru.st>
Cc: 62509@debbugs.gnu.org, Stefan Kangas <stefankangas@gmail.com>
Subject: bug#62509: 30.0.50; Changes to naming for Windows stapshots - PATCH
Date: Wed, 13 Sep 2023 09:11:09 -0700 [thread overview]
Message-ID: <129e9b33-a9e3-ce16-2c2d-bd72450b0064@gmail.com> (raw)
In-Reply-To: <CAJf-WoTDSrxE0EmUNxC2w=uXcgfswgoA7ijMb3SHHYt4Z=VBLA@mail.gmail.com>
On 9/13/2023 6:06 AM, Corwin Brust wrote:
> That's helpful. I was under the impression we published snapshots for
> developers and didn't typically direct users to use them at all
> (except for pre-release snaps and special circumstances such as
> recently when glibc got several potentially breaking changes.
Well, I think this would mainly be useful for the more-enthusiastic
users who want to try out new things or are impatiently waiting for some
bugfix only on the dev version. I'm not sure whether the actual Emacs
maintainers would direct users to the snapshots, but third-party package
authors might.
> I'm still puzzled as to why we should exclude the time component.
> Wouldn't that be rather more useful than including the date alone for
> those looking to see what revision is that last included (but doing so
> without referencing git logs)?
Including the time is fine too. I'm not sure how much value there is in
that (personally, I'd only ever use the date for an approximate value of
"how new is this"), but it doesn't cause any harm.
prev parent reply other threads:[~2023-09-13 16:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 22:29 bug#62509: 30.0.50; Changes to naming for Windows stapshots - PATCH Corwin Brust
2023-09-01 19:39 ` Stefan Kangas
2023-09-13 2:33 ` Corwin Brust
2023-09-13 4:14 ` Jim Porter
2023-09-13 12:12 ` Stefan Kangas
2023-09-13 13:09 ` Corwin Brust
2023-09-13 13:06 ` Corwin Brust
2023-09-13 13:11 ` Stefan Kangas
2023-09-13 16:11 ` Jim Porter [this message]
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=129e9b33-a9e3-ce16-2c2d-bd72450b0064@gmail.com \
--to=jporterbugs@gmail.com \
--cc=62509@debbugs.gnu.org \
--cc=corwin@bru.st \
--cc=stefankangas@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 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).