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

indent: Fix spelling

Browse source 
--

These are non-substantive corrections for minor spelling mistakes
within the GnuPG codebase.

With something like this applied to the codebase, and a judiciously
tuned spellchecker integrated as part of a standard test suite, it
should be possible to keep a uniform orthography within the project.

GnuPG-bug-id: 7116
This commit is contained in:
Daniel Kahn Gillmor 2024-05-12 18:09:23 -04:00 • committed by Werner Koch
parent 253a701ed7
commit 42b0e9558a
No known key found for this signature in database
GPG key ID: E3FDFF218E45B72B
136 changed files with 233 additions and 233 deletions
Download patch file Download diff file Expand all files Collapse all files

4
doc/HACKING
View file

@ -152,7 +152,7 @@ Note that such a comment will be removed if the git commit option
if ( 42 == foo )
#+end_src
this is harder to read and modern compilers are pretty good in
detecing accidental assignments. It is also suggested not to
detecting accidental assignments. It is also suggested not to
compare to 0 or NULL but to test the value direct or with a '!';
this makes it easier to see that a boolean test is done.
- We use our own printf style functions like =es_printf=, and
@ -244,7 +244,7 @@ subject line; the list is used for several different projects.
In general you should send patches only for the master branch; we may
later decide to backport to another branch. Please ask first before
sending pacthes for another branch.
sending patches for another branch.
If you're working from the Git repo, here's a suggested workflow: