all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ng0 <contact.ng0@cryptolab.net>
To: David Craven <david@craven.ch>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Commits signed by key not registered on Savannah
Date: Sun, 12 Feb 2017 11:19:00 +0000	[thread overview]
Message-ID: <20170212111900.scgyf6q75y7sk2pg@wasp> (raw)
In-Reply-To: <CAL1_imk6zU6sBk_uGb_jXg++8UVc--DKLoD6MtsaikjC+hOQ7Q@mail.gmail.com>

On 17-02-12 00:41:38, David Craven wrote:
> > It might be nice to associate with each committer, a list of all keys
> > that they have ever used to sign commits in our git repository.
> 
> > Keys would be added to the list over time, but never removed.
> 
> Sounds good. Where would we put that list? And does that list also

Would the git repository, or a new git repository (guix-keys.git?) be a
bad idea? Best case, we craft something which serves as an GNUPG_HOME
for the keys which then live in the keyring of this thing (compare to
gentoo-keys, debian-keys, etc).

> need to be signed? Puh, lucky for me I don't have to be responsible
> for that key =P
> 
> For now my public keys are published on mit.edu, so they shouldn't be lost
> and can be retrieved when this list materializes.
> 
> >  The conventional usage of Savannah's ssh key registry is to include only
> > currently active keys, and that's needed as well.
> 
> I updated the key.
> 

-- 
ng0 -- https://www.inventati.org/patternsinthechaos/

  reply	other threads:[~2017-02-12 11:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20170210161608.9175.4763@vcs0.savannah.gnu.org>
     [not found] ` <20170210161610.BD4DB21058@vcs0.savannah.gnu.org>
2017-02-11 10:05   ` Commits signed by key not registered on Savannah Mark H Weaver
2017-02-11 13:49     ` David Craven
2017-02-11 14:35       ` Ludovic Courtès
2017-02-11 21:11       ` Mark H Weaver
2017-02-11 22:16         ` Mark H Weaver
2017-02-11 23:41           ` David Craven
2017-02-12 11:19             ` ng0 [this message]
2017-02-12 12:26               ` David Craven
2017-02-12 13:43                 ` Ludovic Courtès
2017-02-12 21:55                 ` Mark H Weaver
2017-02-12 23:01                   ` Leo Famulari

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=20170212111900.scgyf6q75y7sk2pg@wasp \
    --to=contact.ng0@cryptolab.net \
    --cc=david@craven.ch \
    --cc=guix-devel@gnu.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/guix.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.