From e982d5118e9056e2e08810fa6ca24cf7c24495b9 Mon Sep 17 00:00:00 2001 From: Peter Hutterer Date: Wed, 3 May 2017 11:16:30 +1000 Subject: [PATCH] docs: clarify that vcs_tag output can be used as source "you should put in your main program" is confusing, "that can be used as source" is slightly better. --- docs/markdown/Reference-manual.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/markdown/Reference-manual.md b/docs/markdown/Reference-manual.md index 116fd58f4..cbcbbdc0a 100644 --- a/docs/markdown/Reference-manual.md +++ b/docs/markdown/Reference-manual.md @@ -641,7 +641,7 @@ This command detects revision control commit information at build time and place - `output` file to write the results to (e.g. `version.c`) - `fallback` version number to use when no revision control information is present, such as when building from a release tarball -Meson will read the contents of `input`, replace the string `@VCS_TAG@` with the detected revision number and write the result to `output`. This method returns an opaque [`custom_target`](#custom_target) object that you should put in your main program. If you desire more specific behavior than what this command provides, you should use `custom_target`. +Meson will read the contents of `input`, replace the string `@VCS_TAG@` with the detected revision number and write the result to `output`. This method returns an opaque [`custom_target`](#custom_target) object that can be used as source. If you desire more specific behavior than what this command provides, you should use `custom_target`. ## Built-in objects