security-and-privacy/gnupg
security-and-privacy/gnupg
1
0
Fork 0
mirror of git://git.gnupg.org/gnupg.git synced 2025-07-02 22:46:30 +02:00
Code Activity

indent: Some typo and indentation changes for gpg.

Browse source 
--
This commit is contained in:
Werner Koch 2020-04-15 22:23:10 +02:00
parent df0edaf91a
commit 5c47e7825b
No known key found for this signature in database
GPG key ID: E3FDFF218E45B72B
5 changed files with 18 additions and 19 deletions
Download patch file Download diff file Expand all files Collapse all files

7
doc/HACKING
View file

@ -182,12 +182,11 @@ Note that such a comment will be removed if the git commit option
** Variable names
Follow the GNU standards. Here are some conventions you may want to
stick to (do not rename existing "wrong" uses without a goog
reason).
stick to (do not rename existing "wrong" uses without a good reason).
- err :: This conveys an error code of type =gpg_error_t= which is
compatible to an =int=. To compare such a variable to a
GPG_ERR_ constant, it is necessary to map the value like
GPG_ERR_ constant, it is necessary to access the value like
this: =gpg_err_code(err)=.
- ec :: This is used for a gpg-error code which has no source part
(=gpg_err_code_t=) and will eventually be used as input to
@ -425,5 +424,3 @@ plaintext packets and so on. The file g10/encode.c might be a good
starting point to see how it is used - actually this is the other way:
constructing messages using pushed filters but it may be easier to
understand.