From 1db800bf67fc80abee313381aac0528ee33103c9 Mon Sep 17 00:00:00 2001 From: Eli Schwartz Date: Sun, 22 Nov 2020 19:01:49 -0500 Subject: doc: fix confusing use of "build" as a directory argument [skip ci] In most places, we now refer to "builddir/" which is a lot less likely to make people think it is a subcommand which needs to be used literally. This is a regression since commit 276d342ebaf859dd53e145ead3e98e2cebb360ab due to the existence of new docs which were added later on, using the wrong form. --- docs/markdown/Release-notes-for-0.55.0.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs/markdown/Release-notes-for-0.55.0.md') diff --git a/docs/markdown/Release-notes-for-0.55.0.md b/docs/markdown/Release-notes-for-0.55.0.md index cd3f79514..5ee04034b 100644 --- a/docs/markdown/Release-notes-for-0.55.0.md +++ b/docs/markdown/Release-notes-for-0.55.0.md @@ -238,7 +238,7 @@ force fallback for specific subprojects. Example: ``` -meson build --force-fallback-for=foo,bar +meson builddir/ --force-fallback-for=foo,bar ``` ## Implicit dependency fallback -- cgit v1.3