From: Eli Zaretskii <eliz@gnu.org>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: mail@daniel-mendler.de, 61277@debbugs.gnu.org, stefan@marxist.se,
rms@gnu.org, monnier@iro.umontreal.ca
Subject: bug#61277: FR: ELPA security - Restrict package builds to signed git commits
Date: Tue, 07 Feb 2023 14:40:19 +0200 [thread overview]
Message-ID: <83bkm5ps24.fsf@gnu.org> (raw)
In-Reply-To: <87sffh8zts.fsf@localhost> (message from Ihor Radchenko on Tue, 07 Feb 2023 11:44:31 +0000)
> Cc: Daniel Mendler <mail@daniel-mendler.de>, 61277@debbugs.gnu.org,
> stefan@marxist.se, monnier@iro.umontreal.ca
> From: Ihor Radchenko <yantar92@posteo.net>
> Date: Tue, 07 Feb 2023 11:44:31 +0000
>
> Richard Stallman <rms@gnu.org> writes:
>
> > Should we move this to emacs-devel? A specific bug ticket
> > is not the right place for such an important topic.
>
> This was explicitly requested to be made into a bug ticket on
> emacs-devel. See
> https://yhetil.org/emacs-devel/CADwFkmkx3J=LvWT1upGMBaC3MRuyuxmAOB4ghRpYu-BCuX3sSg@mail.gmail.com
The bug report is OK, but we want to discuss more general issues, I
think.
next prev parent reply other threads:[~2023-02-07 12:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-04 18:19 bug#61277: FR: ELPA security - Restrict package builds to signed git commits Daniel Mendler
2023-02-05 11:19 ` Ihor Radchenko
2023-02-07 3:56 ` Richard Stallman
2023-02-07 11:44 ` Ihor Radchenko
2023-02-07 12:40 ` Eli Zaretskii [this message]
2023-02-09 4:28 ` Richard Stallman
2023-02-09 12:07 ` Ihor Radchenko
2023-02-12 4:04 ` Richard Stallman
2023-02-07 12:10 ` Eli Zaretskii
2023-02-12 6:37 ` Stefan Kangas
2023-02-12 10:32 ` Daniel Mendler
2023-02-15 5:17 ` Richard Stallman
2023-02-15 5:17 ` Richard Stallman
2023-02-15 13:37 ` Stefan Kangas
2023-02-15 16:40 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-26 2:59 ` Richard Stallman
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=83bkm5ps24.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=61277@debbugs.gnu.org \
--cc=mail@daniel-mendler.de \
--cc=monnier@iro.umontreal.ca \
--cc=rms@gnu.org \
--cc=stefan@marxist.se \
--cc=yantar92@posteo.net \
/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).