zsh-workers
 help / color / mirror / code / Atom feed
From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: zsh-workers@zsh.org
Subject: Re: Posted zsh 5.9
Date: Sat, 21 May 2022 01:31:09 +0000	[thread overview]
Message-ID: <20220521013109.GA2273@tarpaulin.shahaf.local2> (raw)
In-Reply-To: <YoLk30/vdg6yh4MP@fullerene.field.pennock-tech.net>

Phil Pennock wrote on Mon, May 16, 2022 at 19:57:19 -0400:
> and of those, I'm obviously biased towards
> <https://github.com/PennockTech/openpgpkey-control>; that layout is what
> I use for some other domains, and `other/standalone-update-website`
> within the repo has been successfully used by at least a few people in
> updating contents as part of a general website build flow ... and is
> probably the right path for zsh.org.

FWIW, I use this script for my key and I'm happy with it.

Cheers,

Daniel

>                                       Feed it the keyring for
> `--keys-file` and a directory top for the serving root for
> `--output-dir` and it will write things into the right places.
> 
> With that, `gpg --locate-keys pdp@zsh.org` would work, and similarly for
> any other key with a UID in zsh.org.


  reply	other threads:[~2022-05-21  1:31 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-14 20:59 dana
2022-05-14 21:50 ` Daniel Shahaf
2022-05-14 21:58   ` Daniel Shahaf
2022-05-14 22:27   ` dana
2022-05-14 23:26     ` Daniel Shahaf
2022-05-14 23:28     ` Daniel Shahaf
2022-05-14 23:50       ` dana
2022-05-15 10:36         ` Daniel Shahaf
2022-05-15 21:43           ` dana
2022-05-16 23:57   ` Phil Pennock
2022-05-21  1:31     ` Daniel Shahaf [this message]
2022-05-14 22:11 ` Axel Beckert
2022-05-14 22:31   ` dana
2022-05-15  4:33     ` Bart Schaefer
2022-05-15  6:00       ` dana
2022-05-14 23:21   ` Daniel Shahaf
2022-05-14 23:35     ` Axel Beckert
2022-05-14 23:49       ` Daniel Shahaf

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=20220521013109.GA2273@tarpaulin.shahaf.local2 \
    --to=d.s@daniel.shahaf.name \
    --cc=zsh-workers@zsh.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.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).