From: Leo Famulari <leo@famulari.name>
To: Alex Vong <alexvong1995@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: push right for trivial commits
Date: Thu, 22 Nov 2018 13:08:30 -0500 [thread overview]
Message-ID: <20181122180830.GA30673@jasmine.lan> (raw)
In-Reply-To: <87ftvu6vp6.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 767 bytes --]
On Thu, Nov 22, 2018 at 04:07:33AM +0800, Alex Vong wrote:
> I think ECC key works with commit signing precisely because commit
> signing simply requires Savannah to store the key. However, for
> functionalities provided by Savannah (e.g. sending email to your address
> encrypted with your ECC public key), it wouldn't work (as mentioned in
> <https://savannah.gnu.org/support/?109583>).
To clarify, Savannah doesn't require you to store any key at all in
order to sign Git commits. I think that Savannah accounts don't
integrate with Git at all; they simply offer hosted Git repositories,
and commit signing is a feature of Git.
We require Guix contributors to upload their keys to their Savannah
account so that there is an authoritative source of signing keys.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-11-22 18:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-03 3:44 push right for trivial commits Alex Vong
2018-11-06 11:27 ` Ludovic Courtès
2018-11-10 9:03 ` Alex Vong
2018-11-10 12:45 ` Nils Gillmann
2018-11-11 16:46 ` Ludovic Courtès
2018-11-13 1:45 ` Alex Vong
2018-11-13 1:58 ` Alex Vong
2018-11-13 15:23 ` Leo Famulari
2018-11-13 12:31 ` Nils Gillmann
2018-11-14 5:34 ` Alex Vong
2018-11-14 8:24 ` swedebugia
2018-11-14 10:35 ` Ludovic Courtès
2018-11-19 23:27 ` Nils Gillmann
2018-11-21 20:07 ` Alex Vong
2018-11-22 9:15 ` Ludovic Courtès
2018-11-22 18:08 ` Leo Famulari [this message]
2018-11-22 19:30 ` Alex Vong
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181122180830.GA30673@jasmine.lan \
--to=leo@famulari.name \
--cc=alexvong1995@gmail.com \
--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 public inbox
https://git.savannah.gnu.org/cgit/guix.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).