aboutsummaryrefslogtreecommitdiffstats
path: root/doc/HACKING
diff options
context:
space:
mode:
authorDaniel Kahn Gillmor <[email protected]>2024-05-12 22:09:23 +0000
committerWerner Koch <[email protected]>2024-05-31 10:28:32 +0000
commit42b0e9558a308dbc954ee60c3d346b5cabcd2fdb (patch)
treef073776758cd706a0cadf0bd64073d1669a8d691 /doc/HACKING
parentg13: Adjust for changed gnupg_process_spawn. (diff)
downloadgnupg-42b0e9558a308dbc954ee60c3d346b5cabcd2fdb.tar.gz
gnupg-42b0e9558a308dbc954ee60c3d346b5cabcd2fdb.zip
indent: Fix spelling
-- 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
Diffstat (limited to 'doc/HACKING')
-rw-r--r--doc/HACKING4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/HACKING b/doc/HACKING
index ec04a2e37..cb7e400fc 100644
--- a/doc/HACKING
+++ b/doc/HACKING
@@ -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: