I think that there is a more simple way to catch multiple signatures see below.
Other than that, I like this patch.
Signed-off-by: Tacitus Aedifex
---
gpg-interface.c | 18 ++
1 file changed, 18 insertions(+)
diff --git a/gpg-interface.c b/gpg-interface.c
index db17d65f8
On Wed, Sep 26, 2018 at 02:48:49PM -0700, Junio C Hamano wrote:
We do not want your choice of gpg.program or what kind of
trust you have personally recorded in your ~/.gnupg/ affect how gpg
invoked inside our tests work.
This makes sense to me now. I get what you are saying. The gpg binary inst
On Wed, Sep 26, 2018 at 04:05:02PM -0400, Jeffrey Walton wrote:
I got to look at it today. On Windows:
$ cat ~/.gnupg/gpg-agent.conf
pinentry-program
/usr/local/MacGPG2/libexec/pinentry-mac.app/Contents/MacOS/pinentry-mac
Do you have this app on your system? That path looks like one for a mac
On Wed, Sep 26, 2018 at 10:15:06AM -0700, Junio C Hamano wrote:
Nobody raised this so far as far as I recall; thanks for the first
one to do so, as it is a sign that you are doing something unusual
(e.g. have newer or different version of GPG than most other people)
and others will hit by the sam
I keep getting prompted for my algorithm preferences while running all of the
git test suite:
Set preference list to:
Cipher: AES256, AES192, AES, 3DES
Digest: SHA512, SHA384, SHA256, SHA224, SHA1
Compression: Uncompressed
Features: MDC, Keyserver no-modify
What is the best way
While running `make test` on the git source tree I keep getting asked:
Set preference list to:
Cipher: ...
Digest: ...
etc...
Is there any way to turn that prompt off so that `make test` completes without
any keyboard input?
//tæ
I really like this idea. I've often wanted an integrated bug database like
this. My solution has always been to have a subrepo storing bug reports and
coments in .txt files and then using bash porcelain scripts to make a git-like
interface. I think I like this better. My only nit is Go. That mak
On Fri, Aug 03, 2018 at 06:07:46PM -0400, Jeff King wrote:
There's been some work on this lately. See this patch and the response
thread:
https://public-inbox.org/git/20180409204129.43537-9-mastahy...@gmail.com/
The more recent work focused on just doing the minimum to provide
gpg/gpgsm varian
I'm looking at the existing commit signing and verification
integration and it is all GPG specific. I'm interested in refactoring
the code to have a generic signing/verifying interface so that "drivers"
for other signing tools can be created and other signing tools can be
used (e.g. OpenBSD signify
9 matches
Mail list logo
