aboutsummaryrefslogtreecommitdiff
path: root/Makefile
diff options
context:
space:
mode:
authorMichael J Gruber <git@drmicha.warpmail.net>2016-10-12 15:04:15 +0200
committerJunio C Hamano <gitster@pobox.com>2016-10-12 10:41:59 -0700
commit661a1806819ca98c446f82b19e6c98fa174d33a4 (patch)
treefce87ad1b1ffffc6933ab25a667bb96167de4c8f /Makefile
parent21f862b498925194f8f1ebe8203b7a7df756555b (diff)
downloadgit-661a1806819ca98c446f82b19e6c98fa174d33a4.tar.gz
git-661a1806819ca98c446f82b19e6c98fa174d33a4.tar.xz
gpg-interface: use more status letters
According to gpg2's doc/DETAILS: For each signature only one of the codes GOODSIG, BADSIG, EXPSIG, EXPKEYSIG, REVKEYSIG or ERRSIG will be emitted. gpg1 ("classic") behaves the same (although doc/DETAILS differs). Currently, we parse gpg's status output for GOODSIG, BADSIG and trust information and translate that into status codes G, B, U, N for the %G? format specifier. git-verify-* returns success in the GOODSIG case only. This is somewhat in disagreement with gpg, which considers the first 5 of the 6 above as VALIDSIG, but we err on the very safe side. Introduce additional status codes E, X, Y, R for ERRSIG, EXPSIG, EXPKEYSIG, and REVKEYSIG so that a user of %G? gets more information about the absence of a 'G' on first glance. Requested-by: Alex <agrambot@gmail.com> Signed-off-by: Michael J Gruber <git@drmicha.warpmail.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Makefile')
0 files changed, 0 insertions, 0 deletions