From: Nathan McSween <nwmcsween@gmail.com>
To: git@vger.kernel.org
Subject: [REQ] Allow alternatives to gpg
Date: Sat, 15 Apr 2017 20:10:41 -0700 [thread overview]
Message-ID: <9727e699-d97b-e8f2-ca48-574fc4f014af@gmail.com> (raw)
I would like to try to make git signing pluggable, this would allow for
using tools such as signify[1].
Now I'm wondering if this endeavor is worth taking and what would need
to be changed besides
gpg-interface?
[1] http://man.openbsd.org/signify
next reply other threads:[~2017-04-16 3:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-16 3:10 Nathan McSween [this message]
2017-04-16 4:43 ` [REQ] Allow alternatives to gpg Jeff King
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=9727e699-d97b-e8f2-ca48-574fc4f014af@gmail.com \
--to=nwmcsween@gmail.com \
--cc=git@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).