diff options
author | Christian Grothoff <christian@grothoff.org> | 2021-04-23 23:58:12 +0200 |
---|---|---|
committer | Christian Grothoff <christian@grothoff.org> | 2021-04-23 23:58:34 +0200 |
commit | f630c5a675ca37467b5fba9a3dd41044381ac6ce (patch) | |
tree | 113686bec5c58182de320db503f86fa16f2c8c05 | |
parent | 11f5b0148a8343c776b2562494840ad2963959fb (diff) | |
download | gnunet-f630c5a675ca37467b5fba9a3dd41044381ac6ce.tar.gz gnunet-f630c5a675ca37467b5fba9a3dd41044381ac6ce.zip |
-fix typos
-rw-r--r-- | ChangeLog | 10 | ||||
-rw-r--r-- | README | 18 | ||||
-rwxr-xr-x | bootstrap | 2 | ||||
-rw-r--r-- | doc/index.html | 2 | ||||
-rw-r--r-- | doc/release_policy.rfc.txt | 10 |
5 files changed, 21 insertions, 21 deletions
@@ -2,7 +2,7 @@ Sat, 3 Apr 2021 09:40:46 +0200 (08fe7735b) | |||
2 | handbook: Add section on commit messages and developer branches - Martin Schanzenbach | 2 | handbook: Add section on commit messages and developer branches - Martin Schanzenbach |
3 | 3 | ||
4 | Thu, 1 Apr 2021 00:41:38 +0200 (9f340d5cc) | 4 | Thu, 1 Apr 2021 00:41:38 +0200 (9f340d5cc) |
5 | SETU: added some more perf messurement point for var message size - Elias Summermatter | 5 | SETU: added some more perf measurement point for var message size - Elias Summermatter |
6 | 6 | ||
7 | Thu, 1 Apr 2021 00:15:43 +0200 (12bb61317) | 7 | Thu, 1 Apr 2021 00:15:43 +0200 (12bb61317) |
8 | SETU: fixed some bug in rand element gen and added variable payload for perfmance - Elias Summermatter | 8 | SETU: fixed some bug in rand element gen and added variable payload for perfmance - Elias Summermatter |
@@ -11,7 +11,7 @@ Wed, 31 Mar 2021 11:49:10 +0200 (902331756) | |||
11 | SETU: Added new operation parameters for performance tests - Elias Summermatter | 11 | SETU: Added new operation parameters for performance tests - Elias Summermatter |
12 | 12 | ||
13 | Wed, 31 Mar 2021 11:16:38 +0200 (b5660e0a3) | 13 | Wed, 31 Mar 2021 11:16:38 +0200 (b5660e0a3) |
14 | SETU: imporved tests - Elias Summermatter | 14 | SETU: improved tests - Elias Summermatter |
15 | 15 | ||
16 | Tue, 30 Mar 2021 19:26:40 +0200 (ca4c9eae2) | 16 | Tue, 30 Mar 2021 19:26:40 +0200 (ca4c9eae2) |
17 | UTIL/SCALARPRODUCT: Do not build ECC dlog or scalarproduct with incompatible libgcrypt versions (>=1.9.0) - Martin Schanzenbach | 17 | UTIL/SCALARPRODUCT: Do not build ECC dlog or scalarproduct with incompatible libgcrypt versions (>=1.9.0) - Martin Schanzenbach |
@@ -32,7 +32,7 @@ Thu, 18 Mar 2021 11:48:42 +0100 (f9ae0c23c) | |||
32 | Added working test with randum set - Elias Summermatter | 32 | Added working test with randum set - Elias Summermatter |
33 | 33 | ||
34 | Thu, 18 Mar 2021 08:45:31 +0100 (0d6237ae0) | 34 | Thu, 18 Mar 2021 08:45:31 +0100 (0d6237ae0) |
35 | Added some randum elemet generation test for setu - Elias Summermatter | 35 | Added some randum element generation test for setu - Elias Summermatter |
36 | 36 | ||
37 | Sun, 14 Mar 2021 14:04:00 +0100 (b47586e76) | 37 | Sun, 14 Mar 2021 14:04:00 +0100 (b47586e76) |
38 | add packaging notice; fix #5633 - Martin Schanzenbach | 38 | add packaging notice; fix #5633 - Martin Schanzenbach |
@@ -722,7 +722,7 @@ Thu, 30 Jan 2020 10:48:04 +0100 (015cd279b) | |||
722 | added testing scripts for dns2gns - rexxnor | 722 | added testing scripts for dns2gns - rexxnor |
723 | 723 | ||
724 | Fri, 24 Jan 2020 16:51:29 +0100 (f4a172abf) | 724 | Fri, 24 Jan 2020 16:51:29 +0100 (f4a172abf) |
725 | export GNUNET_PQ_run_sql() functonality - Christian Grothoff | 725 | export GNUNET_PQ_run_sql() functionality - Christian Grothoff |
726 | 726 | ||
727 | Fri, 24 Jan 2020 16:30:45 +0100 (2fd320bc7) | 727 | Fri, 24 Jan 2020 16:30:45 +0100 (2fd320bc7) |
728 | modify GNUNET_PQ_connect_with_cfg to enable flexible loading of .sql files - Christian Grothoff | 728 | modify GNUNET_PQ_connect_with_cfg to enable flexible loading of .sql files - Christian Grothoff |
@@ -902,7 +902,7 @@ Fri Jun 28 14:10:53 2019 +0200 | |||
902 | 902 | ||
903 | Thu Jun 27 10:34:46 2019 +0200 | 903 | Thu Jun 27 10:34:46 2019 +0200 |
904 | The REST server now returns the Origin header value in the | 904 | The REST server now returns the Origin header value in the |
905 | CORS header reponse. -schanzen | 905 | CORS header response. -schanzen |
906 | 906 | ||
907 | Thu Jun 27 09:08:06 2019 +0200 | 907 | Thu Jun 27 09:08:06 2019 +0200 |
908 | GNS NSS plugin will not timeout and not hang forever and block | 908 | GNS NSS plugin will not timeout and not hang forever and block |
@@ -182,7 +182,7 @@ Recommended software for developer tools: | |||
182 | you, open a bug so that we can get a more portable | 182 | you, open a bug so that we can get a more portable |
183 | fix in. | 183 | fix in. |
184 | 184 | ||
185 | [*4] We are commited to portable tools and solutions | 185 | [*4] We are committed to portable tools and solutions |
186 | where possible. New scripts should be Posix sh | 186 | where possible. New scripts should be Posix sh |
187 | compatible, current and older scripts are | 187 | compatible, current and older scripts are |
188 | in the process of being rewritten to comply | 188 | in the process of being rewritten to comply |
@@ -213,7 +213,7 @@ For a correct functionality depending on the host OS, you need | |||
213 | to run the equivalent of these steps after installation. | 213 | to run the equivalent of these steps after installation. |
214 | Replace $(DESTDIR)$(libexecdir) with the appropriate paths, | 214 | Replace $(DESTDIR)$(libexecdir) with the appropriate paths, |
215 | for example /usr/local/lib/gnunet/libexec/. Note that this | 215 | for example /usr/local/lib/gnunet/libexec/. Note that this |
216 | obviously must be run as priviledged user. | 216 | obviously must be run as privileged user. |
217 | 217 | ||
218 | chown root:root $(DESTDIR)$(libexecdir)/gnunet-helper-vpn | 218 | chown root:root $(DESTDIR)$(libexecdir)/gnunet-helper-vpn |
219 | chmod u+s $(DESTDIR)$(libexecdir)/gnunet-helper-vpn | 219 | chmod u+s $(DESTDIR)$(libexecdir)/gnunet-helper-vpn |
@@ -289,8 +289,8 @@ Building GNUnet from source | |||
289 | 289 | ||
290 | IMPORTANT: You can read further notes about compilation from source in | 290 | IMPORTANT: You can read further notes about compilation from source in |
291 | the handbook under doc/handbook/, which includes notes about specific | 291 | the handbook under doc/handbook/, which includes notes about specific |
292 | requirements for operating systems aswell. If you are a package | 292 | requirements for operating systems as well. If you are a package |
293 | mantainer for an Operating System we invite you to add your notes if | 293 | maintainer for an Operating System we invite you to add your notes if |
294 | you feel it is necessary and can not be covered in your Operating | 294 | you feel it is necessary and can not be covered in your Operating |
295 | System's documentation. | 295 | System's documentation. |
296 | 296 | ||
@@ -338,7 +338,7 @@ in 'contrib/services' or by running: | |||
338 | 338 | ||
339 | 339 | ||
340 | Note that you must read paragraph "Notes on setuid", which documents steps you | 340 | Note that you must read paragraph "Notes on setuid", which documents steps you |
341 | have to follow after the installation, as a priviledged user. We require some | 341 | have to follow after the installation, as a privileged user. We require some |
342 | binaries to be setuid. The most portable approach across all supported | 342 | binaries to be setuid. The most portable approach across all supported |
343 | platforms and targets is to let this be handled manually. | 343 | platforms and targets is to let this be handled manually. |
344 | The installation will work if you do not run these steps as root, but some | 344 | The installation will work if you do not run these steps as root, but some |
@@ -376,7 +376,7 @@ $GNUNET_PREFIX you might have specified, as those libraries must be in | |||
376 | your packaging script to miss those plugins, so you might need to do some | 376 | your packaging script to miss those plugins, so you might need to do some |
377 | additional manual work to include those libraries in your binary package(s). | 377 | additional manual work to include those libraries in your binary package(s). |
378 | Similarly, if you want to use the GNUnet Name System and did NOT run | 378 | Similarly, if you want to use the GNUnet Name System and did NOT run |
379 | GNUnet's 'make install' process with priviledged rights, the libraries will be | 379 | GNUnet's 'make install' process with privileged rights, the libraries will be |
380 | installed to "$GNUNET_PREFIX" and you will have to move them to "/lib/" | 380 | installed to "$GNUNET_PREFIX" and you will have to move them to "/lib/" |
381 | manually. | 381 | manually. |
382 | 382 | ||
@@ -443,7 +443,7 @@ GNUnet by periodically executing | |||
443 | $ cat $SERVICEHOME/data/hosts/* > the_file | 443 | $ cat $SERVICEHOME/data/hosts/* > the_file |
444 | 444 | ||
445 | and offering 'the_file' via your web server. Alternatively, you can | 445 | and offering 'the_file' via your web server. Alternatively, you can |
446 | run the build-in web server by adding '-p' to the OPTIONS value | 446 | run the built-in web server by adding '-p' to the OPTIONS value |
447 | in the "hostlist" section of gnunet.conf and opening the respective | 447 | in the "hostlist" section of gnunet.conf and opening the respective |
448 | HTTPPORT to the public. | 448 | HTTPPORT to the public. |
449 | 449 | ||
@@ -495,7 +495,7 @@ https://bugs.gnunet.org/ or our bugs mailinglist. | |||
495 | Please make sure to run the script "contrib/scripts/gnunet-bugreport" | 495 | Please make sure to run the script "contrib/scripts/gnunet-bugreport" |
496 | and include the output with your bug reports. More about how to | 496 | and include the output with your bug reports. More about how to |
497 | report bugs can be found in the GNUnet FAQ on the webpage. Submit | 497 | report bugs can be found in the GNUnet FAQ on the webpage. Submit |
498 | patches via E-Mail to gnunet-developers@gnu.org, formated with | 498 | patches via E-Mail to gnunet-developers@gnu.org, formatted with |
499 | `git format-patch`. | 499 | `git format-patch`. |
500 | 500 | ||
501 | In order to run the unit tests by hand (instead of using "make check"), | 501 | In order to run the unit tests by hand (instead of using "make check"), |
@@ -540,7 +540,7 @@ Then set in the HTTP section of gnunet.conf the "ADVERTISED_PORT" to | |||
540 | "ADVERTISED_PORT" to "443" and "PORT" to 4433. | 540 | "ADVERTISED_PORT" to "443" and "PORT" to 4433. |
541 | 541 | ||
542 | You can do the same trick for the TCP and UDP transports if you want | 542 | You can do the same trick for the TCP and UDP transports if you want |
543 | to map them to a priviledged port (from the point of view of the | 543 | to map them to a privileged port (from the point of view of the |
544 | network). However, we are not aware of this providing any advantages | 544 | network). However, we are not aware of this providing any advantages |
545 | at this point. | 545 | at this point. |
546 | 546 | ||
@@ -1,7 +1,7 @@ | |||
1 | #!/bin/sh | 1 | #!/bin/sh |
2 | # | 2 | # |
3 | # We should use /usr/bin/env sh, but some systems are notoriously picky. | 3 | # We should use /usr/bin/env sh, but some systems are notoriously picky. |
4 | # In fact we could ommit this line if some automations wouldn't rely on | 4 | # In fact we could omit this line if some automations wouldn't rely on |
5 | # running this file via ./bootstrap. | 5 | # running this file via ./bootstrap. |
6 | # | 6 | # |
7 | # This file is in the public domain. | 7 | # This file is in the public domain. |
diff --git a/doc/index.html b/doc/index.html index 93c0e7d9e..bf8683780 100644 --- a/doc/index.html +++ b/doc/index.html | |||
@@ -2,7 +2,7 @@ | |||
2 | <head> | 2 | <head> |
3 | <title>GNUnet - GNUnet Manuals and Handbooks</title> | 3 | <title>GNUnet - GNUnet Manuals and Handbooks</title> |
4 | <meta charset="utf-8"> | 4 | <meta charset="utf-8"> |
5 | <meta name="keywords" content="gnunet,GNUnet,Manual,Manuals,preview,developer-preview,inofficial,GNU"> | 5 | <meta name="keywords" content="gnunet,GNUnet,Manual,Manuals,preview,developer-preview,unofficial,GNU"> |
6 | <meta name="description" content="The GNUnet Manuals"> | 6 | <meta name="description" content="The GNUnet Manuals"> |
7 | <link href="style.css" rel="stylesheet"> | 7 | <link href="style.css" rel="stylesheet"> |
8 | <meta name="viewport" content="width=device-width, initial-scale=1"> | 8 | <meta name="viewport" content="width=device-width, initial-scale=1"> |
diff --git a/doc/release_policy.rfc.txt b/doc/release_policy.rfc.txt index 8fd89f73c..41c98ec93 100644 --- a/doc/release_policy.rfc.txt +++ b/doc/release_policy.rfc.txt | |||
@@ -42,7 +42,7 @@ document the current release model: | |||
42 | mostly we rather explicitly declare certain bugs as "not critical") | 42 | mostly we rather explicitly declare certain bugs as "not critical") |
43 | - Whenever API changes happen the person making that changes should update | 43 | - Whenever API changes happen the person making that changes should update |
44 | dependencies or at least work with people who hack on the dependencies to | 44 | dependencies or at least work with people who hack on the dependencies to |
45 | cooridnate the adjustments | 45 | coordinate the adjustments |
46 | o buildbots are happy (if running) | 46 | o buildbots are happy (if running) |
47 | o static analysis is happy (if available, false-positives => ignore) | 47 | o static analysis is happy (if available, false-positives => ignore) |
48 | o documentation is reasonably up-to-date | 48 | o documentation is reasonably up-to-date |
@@ -57,7 +57,7 @@ For further information see: https://trunkbaseddevelopment.com/ | |||
57 | 57 | ||
58 | II. Evaluation Criteria | 58 | II. Evaluation Criteria |
59 | ======================= | 59 | ======================= |
60 | (what are criterias to interprete the results as success if we review | 60 | (what are criteria to interpret the results as success if we review |
61 | the problem and solution after a year or so) | 61 | the problem and solution after a year or so) |
62 | 62 | ||
63 | III. Concerns (of team members) | 63 | III. Concerns (of team members) |
@@ -74,7 +74,7 @@ code. I don't have a magic bullet to motivate you to write more tests, | |||
74 | or to improve existing tests. -CG | 74 | or to improve existing tests. -CG |
75 | 75 | ||
76 | Your argument is good. Two or three of us thought that the problem is about | 76 | Your argument is good. Two or three of us thought that the problem is about |
77 | missing releases which we feld demotivating. We thought, we were stucked | 77 | missing releases which we feld demotivating. We thought, we were stuck |
78 | somewhere. But as you state, it is us not doing the necessary work. What I | 78 | somewhere. But as you state, it is us not doing the necessary work. What I |
79 | still find useful is to document the release process. In consequence I | 79 | still find useful is to document the release process. In consequence I |
80 | changed the problem statement. -xrs | 80 | changed the problem statement. -xrs |
@@ -125,7 +125,7 @@ leaves of the dependency graph, that is great. However, occasionally | |||
125 | there are architectural changes. Not of the type where the graph | 125 | there are architectural changes. Not of the type where the graph |
126 | changes, but where key API assumptions change. We recently had one for | 126 | changes, but where key API assumptions change. We recently had one for |
127 | the GNU Name System with the dropping of ".gnu". Before, CADET | 127 | the GNU Name System with the dropping of ".gnu". Before, CADET |
128 | changed the semantics and paramter for 'port'. In the future, CORE | 128 | changed the semantics and parameter for 'port'. In the future, CORE |
129 | will introduce protocol versioning. Whenever such a change happens, | 129 | will introduce protocol versioning. Whenever such a change happens, |
130 | it usually falls upon the person making that change to update | 130 | it usually falls upon the person making that change to update |
131 | dependencies as well (or at least to work with people who hack on the | 131 | dependencies as well (or at least to work with people who hack on the |
@@ -175,7 +175,7 @@ Note that none of this really adds up to a "release policy". | |||
175 | V. Previous Versions | 175 | V. Previous Versions |
176 | ==================== | 176 | ==================== |
177 | (if we found some flaws in the solution, and we want to change the | 177 | (if we found some flaws in the solution, and we want to change the |
178 | release policy, we document the old ones here als previous versions. | 178 | release policy, we document the old ones here as previous versions. |
179 | the goal is establish a learn process.) | 179 | the goal is establish a learn process.) |
180 | 180 | ||
181 | IV. References | 181 | IV. References |