On 11.08.25 01:37, Adriano Carvalho wrote:
This pattern was prevalent (although not intirely) in the existing text.
Signed-off-by: Adriano Carvalho <adrianocarvalho...@gmail.com>
I agree that we should use the same capitalization everywhere.
But isn't Buildman a proper noun?
Best regards
Heinrich
---
tools/buildman/buildman.rst | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/tools/buildman/buildman.rst b/tools/buildman/buildman.rst
index 48938044520..d5d22732088 100644
--- a/tools/buildman/buildman.rst
+++ b/tools/buildman/buildman.rst
@@ -119,7 +119,7 @@ them later using -se. Note that buildman will assume that
the source has
changed, and will build all specified boards in this case.
Buildman is optimised for building many commits at once, for many boards.
-On multi-core machines, Buildman is fast because it uses most of the
+On multi-core machines, buildman is fast because it uses most of the
available CPU power. When it gets to the end, or if you are building just
a few commits or boards, it will be pretty slow. As a tip, if you don't
plan to use your machine for anything else, you can use -T to increase the
@@ -1021,7 +1021,7 @@ cycle through various different configurations, one per
board built by the
thread. Variations in the configuration will force a rebuild of affected
source
files when a thread switches between boards. Ideally, such buildman-induced
rebuilds would not happen, thus allowing the build to operate as efficiently
as
-the build system and source changes allow. buildman's -P flag may be used to
+the build system and source changes allow. Buildman's -P flag may be used to
enable this; -P causes each board to be built in a separate (board-specific)
directory, thus avoiding any buildman-induced configuration changes in any
build directory.
@@ -1130,10 +1130,10 @@ these when present in defconfig files and handle the
resuiting Kconfig
correctly. Thus it is possible to build a board which has a ``#include`` in
the
defconfig file.
-For now, Buildman simply includes the files to produce a single output file,
+For now, buildman simply includes the files to produce a single output file,
using the C preprocessor. It does not call the ``merge_config.sh`` script. The
redefined/redundant logic in that script could fairly easily be repeated in
-Buildman, to detect potential problems. For now it is not clear that this is
+buildman, to detect potential problems. For now it is not clear that this is
useful.
To specify the C preprocessor to use, set the ``CPP`` environment variable. The
@@ -1144,7 +1144,7 @@ like::
make qemu_riscv64_defconfig acpi.config
-This is partly because there is no way for Buildman to know which fragments are
+This is partly because there is no way for buildman to know which fragments are
valid on which boards.
Building with clang
@@ -1301,7 +1301,7 @@ with -E, e.g. the migration warnings::
...
====================================================
-When doing builds, Buildman's return code will reflect the overall result::
+When doing builds, buildman's return code will reflect the overall result::
0 (success) No errors or warnings found
100 Errors found
