Commit 978027

2025-03-19 09:18:58 Samuli Seppänen: -/-
Archived/ACKSystemReview.md ..
@@ 12,7 12,7 @@
The hypothesis is that the ACK/NACK process is most suitable for reviewing individual patches or small patchsets sent to the openvpn-devel mailing list by developers not intimately familiar with OpenVPN. A less bureaucratic process might be more suitable for core developers, especially when less security-sensitive parts are being modified.
- # Current ACK/NACK code review system =
+ # Current ACK/NACK code review system
## Scope
@@ 172,11 172,11 @@
For comparison, let's look at two big patchsets:
- * [PolarSSL support](/PolarSSLintegration) (~115 patches)
+ * PolarSSL support (~115 patches)
* total of 8 changes were asked for
* 3 of these seem trivial stylistic issues/typos
- * [Buildsystem revolution](/GenericBuildsystemIntegration) (52 patches)
+ * Buildsystem revolution (52 patches)
* a couple of changes were asked for (e.g. to enable lzo by default)
# Conclusions
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9