From: Andrew Savchenko <bircoph@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] repo/gentoo.git, or how committing is challenging
Date: Sun, 13 Dec 2015 21:50:39 +0300 [thread overview]
Message-ID: <20151213215039.fdbaec6a7d5248e82fb882ac@gentoo.org> (raw)
In-Reply-To: <566DAD2F.1010100@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 668 bytes --]
Hi,
On Sun, 13 Dec 2015 18:38:55 +0100 Patrick Lauer wrote:
> On 12/13/2015 06:36 PM, Patrick Lauer wrote:
> > So apparently we're signing things with gpg now
>
> And a related question:
>
> How would I actually verify the signatures in a meaningful way?
git log --show-signature does this using GnuPG.
Of course, in order to gpg to work one have to mark dev keys as
trusted, they can be verified using ldap or several public
keyservers. LDAP is more reliable, of course, but this method works
only for devs (and probably some stuff members) having an access
here.
> ... and why is that not default then.
Best regards,
Andrew Savchenko
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-12-13 18:51 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-13 17:36 [gentoo-dev] repo/gentoo.git, or how committing is challenging Patrick Lauer
2015-12-13 17:38 ` Patrick Lauer
2015-12-13 18:50 ` Andrew Savchenko [this message]
2015-12-13 19:05 ` Patrick Lauer
2015-12-13 19:20 ` Andrew Savchenko
2015-12-13 21:30 ` Mike Gilbert
2015-12-13 21:53 ` Andrew Savchenko
2015-12-14 3:00 ` Brian Dolbec
2015-12-14 6:23 ` Daniel Campbell
2015-12-14 11:12 ` Patrick Lauer
2015-12-14 17:52 ` Mike Gilbert
2015-12-15 0:31 ` Peter Stuge
2015-12-21 3:21 ` [gentoo-dev] " Ryan Hill
2015-12-21 18:59 ` Peter Stuge
2015-12-22 0:45 ` Rich Freeman
2015-12-22 9:41 ` Patrick Lauer
2015-12-22 12:08 ` Rich Freeman
2015-12-22 12:53 ` Patrick Lauer
2015-12-22 13:14 ` Rich Freeman
2015-12-22 13:31 ` Patrick Lauer
2015-12-22 14:04 ` Rich Freeman
2015-12-22 18:21 ` Patrick Lauer
2015-12-22 23:55 ` Peter Stuge
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=20151213215039.fdbaec6a7d5248e82fb882ac@gentoo.org \
--to=bircoph@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox