docs/manual: small typo fixes and cleanup
PATCH 1/1 docs/manual: small typo fixes and cleanup
Fix a few punctuation mistakes. The removed link is redundant, see the previous sentence.
Signed-off-by Merlin B?ge <[email protected]>
--- docs/manual/common-usage.txt | 2 +- docs/manual/customize-patches.txt | 2 +- docs/manual/customize-rootfs.txt | 2 +- docs/manual/writing-rules.txt | 4 ++-- 4 files changed, 5 insertions(+), 5 deletions(-)
docs/manual/common-usage.txt +1 -1
@@ -88,7 +88,7 @@ to +make+ or set in the environment: Buildroot stores the cached files when using ccache. + * +BR2_DL_DIR+ to override the directory in which - Buildroot stores/retrieves downloaded files + Buildroot stores/retrieves downloaded files. + Note that the Buildroot download directory can also be set from the configuration interface, so through the Buildroot +.config+ file. See
docs/manual/customize-patches.txt +1 -1
@@ -53,7 +53,7 @@ directory. The exception to +BR2_GLOBAL_PATCH_DIR+ being the preferred method for specifying custom patches is +BR2_LINUX_KERNEL_PATCH+. +BR2_LINUX_KERNEL_PATCH+ should be used to specify kernel patches that -are available at an URL. *Note:* +BR2_LINUX_KERNEL_PATCH+ specifies kernel +are available at a URL. *Note:* +BR2_LINUX_KERNEL_PATCH+ specifies kernel patches that are applied after patches available in +BR2_GLOBAL_PATCH_DIR+, as it is done from a post-patch hook of the Linux package.
docs/manual/customize-rootfs.txt +1 -1
@@ -145,7 +145,7 @@ It is recommended to use the existing mechanisms to set file permissions The difference between post-build scripts (above) and fakeroot scripts, is that post-build scripts are not called in the fakeroot context. + -.Note; +.Note: Using `fakeroot` is not an absolute substitute for actually being root. `fakeroot` only ever fakes the file access rights and types (regular, block-or-char device...) and uid/gid; these are emulated in-memory.
docs/manual/writing-rules.txt +2 -2
@@ -141,8 +141,8 @@ endif The documentation uses the http://www.methods.co.nz/asciidoc/[asciidoc] format. -For further details about the http://www.methods.co.nz/asciidoc/[asciidoc] -syntax, refer to http://www.methods.co.nz/asciidoc/userguide.html[]. +For further details about the asciidoc syntax, refer to +http://www.methods.co.nz/asciidoc/userguide.html[]. === Support scripts
Signature · 1 line
2.25.2
Yann E. MORIN
AppliedPATCH 1/1 docs/manual: small typo fixes and cleanup
Merlin, All,
On 2020-03-28 15:41 +0100, Merlin B?ge spake thusly:
Quoted 4 lines
Fix a few punctuation mistakes. The removed link is redundant, see the previous sentence.
Signed-off-by Merlin B?ge <[email protected]>
Applied to master, thanks!
Regards,
Yann E. MORIN.
Quoted 68 lines
--- docs/manual/common-usage.txt | 2 +- docs/manual/customize-patches.txt | 2 +- docs/manual/customize-rootfs.txt | 2 +- docs/manual/writing-rules.txt | 4 ++-- 4 files changed, 5 insertions(+), 5 deletions(-)docs/manual/common-usage.txt +1
-1@@ -88,7 +88,7 @@ to +make+ or set in the environment: Buildroot stores the cached files when using ccache. + * +BR2_DL_DIR+ to override the directory in which - Buildroot stores/retrieves downloaded files + Buildroot stores/retrieves downloaded files. + Note that the Buildroot download directory can also be set from the configuration interface, so through the Buildroot +.config+ file. Seedocs/manual/customize-patches.txt +1
-1@@ -53,7 +53,7 @@ directory. The exception to +BR2_GLOBAL_PATCH_DIR+ being the preferred method for specifying custom patches is +BR2_LINUX_KERNEL_PATCH+. +BR2_LINUX_KERNEL_PATCH+ should be used to specify kernel patches that -are available at an URL. *Note:* +BR2_LINUX_KERNEL_PATCH+ specifies kernel +are available at a URL. *Note:* +BR2_LINUX_KERNEL_PATCH+ specifies kernel patches that are applied after patches available in +BR2_GLOBAL_PATCH_DIR+, as it is done from a post-patch hook of the Linux package.docs/manual/customize-rootfs.txt +1
-1@@ -145,7 +145,7 @@ It is recommended to use the existing mechanisms to set file permissions The difference between post-build scripts (above) and fakeroot scripts, is that post-build scripts are not called in the fakeroot context. + -.Note; +.Note: Using `fakeroot` is not an absolute substitute for actually being root. `fakeroot` only ever fakes the file access rights and types (regular, block-or-char device...) and uid/gid; these are emulated in-memory.docs/manual/writing-rules.txt +2
-2@@ -141,8 +141,8 @@ endif The documentation uses the http://www.methods.co.nz/asciidoc/[asciidoc] format. -For further details about the http://www.methods.co.nz/asciidoc/[asciidoc] -syntax, refer to http://www.methods.co.nz/asciidoc/userguide.html[]. +For further details about the asciidoc syntax, refer to +http://www.methods.co.nz/asciidoc/userguide.html[]. === Support scriptsSignature · 6 lines
2.25.2 _______________________________________________ buildroot mailing list buildroot at busybox.net http://lists.busybox.net/mailman/listinfo/buildroot
Signature · 6 lines
.-----------------.--------------------.------------------.--------------------. | Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: | | +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ | | +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no | | http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. | '------------------------------^-------^------------------^--------------------'
PATCH 1/1 docs/manual: small typo fixes and cleanup
In reply to Merlin BügeQuoted 6 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
"Merlin" == Merlin B?ge <[email protected]> writes:
Fix a few punctuation mistakes. The removed link is redundant, see the previous sentence.
Signed-off-by Merlin B?ge <[email protected]>
Committed to 2019.02.x, 2019.11.x and 2020.02.x, thanks.
Signature · 1 line
Bye, Peter Korsgaard