aboutsummaryrefslogtreecommitdiffstats
path: root/lang/cpp/src/verificationresult.cpp
diff options
context:
space:
mode:
authorAndre Heinecke <[email protected]>2016-12-07 20:41:34 +0000
committerAndre Heinecke <[email protected]>2016-12-07 20:46:24 +0000
commit7880335273382f05cbbe38aa965a566c4127ba6a (patch)
tree920374b7c36d348a544e104f258b6d0b35f06043 /lang/cpp/src/verificationresult.cpp
parentpython: Try to be more helpful when given a string to encrypt(). (diff)
downloadgpgme-7880335273382f05cbbe38aa965a566c4127ba6a.tar.gz
gpgme-7880335273382f05cbbe38aa965a566c4127ba6a.zip
Clarify what "checking on bit" means
* doc/gpgme.texi (gpgme_sigsum_t summary): Clarify what "you can check one bit means" -- It was unclear which bit to test for is. And tests with students have shown that they would "test" for this one bit by using if(sig.summary == GPGME_SIGSUM_VALID) which would fail because valid sigs are also SIGSUM_GREEN. So lets give an example for people not used to checking bits and clarify through this example which bit is meant to be checked.
Diffstat (limited to '')
0 files changed, 0 insertions, 0 deletions