unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: philipk@posteo.net, emacs-devel@gnu.org
Subject: Re: [PATCH] Fix random selection of keyserver
Date: Mon, 31 May 2021 14:45:13 +0300	[thread overview]
Message-ID: <83h7ij2kl2.fsf@gnu.org> (raw)
In-Reply-To: <875yyzgtvk.fsf@gnus.org> (message from Lars Ingebrigtsen on Mon,  31 May 2021 11:00:47 +0200)

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: Eli Zaretskii <eliz@gnu.org>,  emacs-devel@gnu.org
> Date: Mon, 31 May 2021 11:00:47 +0200
> 
> Philip Kaludercic <philipk@posteo.net> writes:
> 
> > Perhaps, the intent of this patch was just to fix the currently broken
> > behaviour suggested by epa-keyserver's type.
> >
> > I am not sure if a :set function could be used to randomize the
> > keyserver for every request. Then again, is might not even really be
> > necessary to provide such a feature.
> 
> I wonder whether it might make sense instead to allow `epa-keyserver' to
> be a list, and if so, then choose a random server from that list.
> That'd give users control over what servers to use when randomising. 

Yes, that's what I meant: make the :set function generate the list
from which we then randomly select.  Sorry for unclear wording.



      parent reply	other threads:[~2021-05-31 11:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-30 18:36 [PATCH] Fix random selection of keyserver Philip Kaludercic
2021-05-30 18:57 ` Eli Zaretskii
2021-05-30 19:46   ` Philip Kaludercic
2021-05-31  9:00     ` Lars Ingebrigtsen
2021-05-31 11:13       ` Philip Kaludercic
2021-05-31 11:43         ` Andreas Schwab
2021-05-31 12:04           ` Philip Kaludercic
2021-06-01  5:49         ` Lars Ingebrigtsen
2021-05-31 11:45       ` Eli Zaretskii [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=83h7ij2kl2.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.org \
    --cc=philipk@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).