all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Richard Copley <rcopley@gmail.com>
To: Stephen Leake <stephen_leake@stephe-leake.org>
Cc: Emacs Development <emacs-devel@gnu.org>
Subject: Re: Future release of emacs-26
Date: Fri, 17 May 2019 07:17:30 +0100	[thread overview]
Message-ID: <CAPM58ogPQ9Z9xLb_EaqL2y1nTp5rfXOvysK6dhTZMH0-Jmz+Aw@mail.gmail.com> (raw)
In-Reply-To: <jwv7eapyed1.fsf-monnier+emacs@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 696 bytes --]

On Fri, 17 May 2019 at 04:05, Stefan Monnier <monnier@iro.umontreal.ca>
wrote:

> >> No, this setting is to make it easier for the other ELPA archives which
> >> (AFAIK) don't sign their packages (and in any case, Emacs doesn't come
> >> with the keys for those).
> > Perhaps package-check-signatures should be per-repository, so we are
> > warned when the Gnu ELPA signature check fails.
>
> You should be loudly warned already, if you use the default value
> (unless you don't have GPG installed, IIRC).
>

Also, you can get the effect of per-repository package-check-signatures
using
the defcustom 'package-unsigned-archives' ("List of archives where we do not
check for package signatures").

[-- Attachment #2: Type: text/html, Size: 1194 bytes --]

  reply	other threads:[~2019-05-17  6:17 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-06  4:55 bug#34341: 26.1; url-retrieve-synchronously returns blank buffer Laurent Charignon
2019-02-06  8:12 ` bug#34341: Seems fixed in latest master 5259fdf96073febd18e83785960c443bdf02a310 Laurent Charignon
2019-02-09 18:08 ` bug#34341: more observations Mikhail Rudenko
2019-05-04 15:18 ` bug#34341: 26.1; url-retrieve-synchronously returns blank buffer Noam Postavsky
2019-05-06 11:52   ` Robert Pluim
2019-05-06 12:10     ` Noam Postavsky
2019-05-06 12:15       ` Robert Pluim
2019-05-06 15:21         ` Eli Zaretskii
2019-05-07  0:16           ` Noam Postavsky
2019-05-07  2:36             ` Eli Zaretskii
2019-05-07  6:35             ` Robert Pluim
2019-05-12 13:01               ` Robert Pluim
2019-05-12 14:02                 ` Eli Zaretskii
2019-05-12 14:55                   ` Robert Pluim
2019-05-12 15:23                     ` Eli Zaretskii
2019-05-12 15:39                       ` Robert Pluim
2019-05-12 16:01                         ` Eli Zaretskii
2019-05-14  0:21                 ` Noam Postavsky
2019-05-14  0:34           ` Future release of emacs-26 (WAS: bug#34341) Noam Postavsky
2019-05-14 12:11             ` Nicolas Petton
2019-05-14 13:25             ` Future release of emacs-26 Stefan Monnier
2019-05-14 15:32             ` Future release of emacs-26 (WAS: bug#34341) Eli Zaretskii
2019-05-14 20:34             ` Richard Copley
2019-05-14 21:03               ` Future release of emacs-26 Stefan Monnier
2019-05-14 21:28                 ` Richard Copley
2019-05-15  1:27                   ` Stefan Monnier
2019-05-17  0:03                     ` Stephen Leake
2019-05-17  3:03                       ` Stefan Monnier
2019-05-17  6:17                         ` Richard Copley [this message]
2019-05-22 16:07             ` Phillip Lord
2019-05-22 16:26               ` Stefan Monnier
2019-05-22 17:04               ` Eli Zaretskii
2019-05-23 10:09                 ` Leo Liu
2019-05-27  9:05                 ` Phillip Lord
2019-05-27 16:13                   ` Eli Zaretskii
2019-05-27 20:17                     ` Richard Stallman
2019-05-28  2:37                       ` Eli Zaretskii
2019-05-28 21:41                     ` Noam Postavsky
2019-06-02 18:42                     ` Phillip Lord
2019-06-02 20:34                       ` Stefan Monnier
2019-06-03 14:22                     ` Noam Postavsky
2019-06-03 14:53                       ` Eli Zaretskii
2019-06-03 15:45                         ` Noam Postavsky
2019-06-03 16:00                           ` 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=CAPM58ogPQ9Z9xLb_EaqL2y1nTp5rfXOvysK6dhTZMH0-Jmz+Aw@mail.gmail.com \
    --to=rcopley@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=stephen_leake@stephe-leake.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.