unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
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: Tue, 13 Nov 2018 10:23:44 -0500	[thread overview]
Message-ID: <20181113152344.GA25102@jasmine.lan> (raw)
In-Reply-To: <87k1lhzqk7.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 568 bytes --]

On Tue, Nov 13, 2018 at 09:58:32AM +0800, Alex Vong wrote:
> In the discussion, it was mentioned that the GnuPG version installed on
> Savannah is 1.4.16. Therefore, savannah cannot send encrypted messages
> to me using my ECC key. However, I am not sure about signing commits
> with ECC key. Does it works in Savannah?

Yes, you can still use your ECC key to sign commits. This is a feature
of Git, not Savannah, so it shouldn't matter which version of GnuPG
Savannah is using internally. As far as I know, Savannah doesn't do
anything related to Git commit signing.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2018-11-13 15:25 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 [this message]
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
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=20181113152344.GA25102@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).