security-and-privacy/gnupg
security-and-privacy/gnupg
1
0
Fork 0
mirror of git://git.gnupg.org/gnupg.git synced 2025-01-03 12:11:33 +01:00
Code Activity

doc: Clarify C90 exceptions and add a new commit tag.

Browse Source 
--

The variable definition inside a for statement require to use a c99
option for gcc which we do not want.  It has never been used and thus
we drop it.

Signed-off-by: Werner Koch <wk@gnupg.org>
This commit is contained in:
Werner Koch 2017-12-08 13:44:24 +01:00
parent 84af0bcca3
commit 6d14be22a1
No known key found for this signature in database
GPG Key ID: E3FDFF218E45B72B
1 changed files with 4 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
doc/HACKING
View File

@ -33,9 +33,9 @@ not be copied to the ChangeLog, separate it by a line consisting of
two dashes at the begin of a line. two dashes at the begin of a line.
The one-line summary usually starts with a keyword to identify the The one-line summary usually starts with a keyword to identify the
mainly affected subsystem. If more than one keyword is required the mainly affected subsystem (that is not the directory). If more than
are delimited by a comma (e.g. =scd,w32:=). Commonly found keywords one keyword is required they are delimited by a comma
are (e.g. =scd,w32:=). Commonly found keywords are
- agent :: The gpg-agent component - agent :: The gpg-agent component
- build :: Changes to the build system - build :: Changes to the build system
@ -207,10 +207,6 @@ Note that such a comment will be removed if the git commit option
- The predefined macro =__func__=: - The predefined macro =__func__=:
: log_debug ("%s: Problem with foo\n", __func__); : log_debug ("%s: Problem with foo\n", __func__);
- Variable declaration inside a for():
: for (int i = 0; i < 5; ++)
: bar (i);
Although we usually make use of the =u16=, =u32=, and =u64= types, Although we usually make use of the =u16=, =u32=, and =u64= types,
it is also possible to include =<stdint.h>= and use =int16_t=, it is also possible to include =<stdint.h>= and use =int16_t=,
=int32_t=, =int64_t=, =uint16_t=, =uint32_t=, and =uint64_t=. But do =int32_t=, =int64_t=, =uint16_t=, =uint32_t=, and =uint64_t=. But do
@ -224,6 +220,7 @@ Note that such a comment will be removed if the git commit option
- CVE-id :: CVE id number pertaining to this commit. - CVE-id :: CVE id number pertaining to this commit.
- Regression-due-to :: Commit id of the regression fixed by this commit. - Regression-due-to :: Commit id of the regression fixed by this commit.
- Fixes-commit :: Commit id this commit fixes. - Fixes-commit :: Commit id this commit fixes.
- Updates-commit :: Commit id this commit updates.
- Reported-by :: Value is a name or mail address of a bug reporte. - Reported-by :: Value is a name or mail address of a bug reporte.
- Suggested-by :: Value is a name or mail address of someone how - Suggested-by :: Value is a name or mail address of someone how
suggested this change. suggested this change.