From: Lars Ingebrigtsen <larsi@gnus.org>
To: Corwin Brust <corwin@bru.st>
Cc: 55082@debbugs.gnu.org, Matthew James Kraai <kraai@ftbfs.org>
Subject: bug#55082: emacs-28.1-installer.exe not signed by Phillip Lord
Date: Sat, 23 Apr 2022 22:06:45 +0200 [thread overview]
Message-ID: <8735i3ef8q.fsf@gnus.org> (raw)
In-Reply-To: <CAJf-WoS80q9dMVHU1wrFOxsF9btz5NbNiE1nt6D_VukgM_EE2Q@mail.gmail.com> (Corwin Brust's message of "Sat, 23 Apr 2022 14:55:44 -0500")
Corwin Brust <corwin@bru.st> writes:
> Apropos, I notice there's no mention of the executable installer on
> the page either. Would it make sense for me to try preparing a second
> patch to provide some information about the binary release versions we
> currently produce for MS Windows?
What kind of information did you have in mind? I think that web page
should be kept as concise as possible, with the bare minimum of talk
beyond how to download things on various platforms.
> If so, is it worth having a new bug report to keep track of that
> seperately that work/discussion separately?
No, discussing that's fine here.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-04-23 20:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-23 16:26 bug#55082: emacs-28.1-installer.exe not signed by Phillip Lord Matthew James Kraai
2022-04-23 18:30 ` Corwin Brust
2022-04-23 18:34 ` Lars Ingebrigtsen
2022-04-23 18:51 ` Corwin Brust
2022-04-23 19:55 ` Corwin Brust
2022-04-23 20:06 ` Lars Ingebrigtsen [this message]
2022-04-23 20:34 ` Corwin Brust
2022-04-24 5:15 ` Eli Zaretskii
2022-04-24 5:43 ` Corwin Brust
2022-04-24 6:16 ` Eli Zaretskii
2022-04-24 6:22 ` Corwin Brust
2022-04-24 6:31 ` Corwin Brust
2022-04-24 11:18 ` Lars Ingebrigtsen
2022-04-24 15:29 ` Corwin Brust
2022-04-24 23:56 ` Matthew James Kraai
2022-04-23 19:59 ` Lars Ingebrigtsen
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=8735i3ef8q.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=55082@debbugs.gnu.org \
--cc=corwin@bru.st \
--cc=kraai@ftbfs.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).