"up-to-date" should only use hyphens when used as compound modifier of a noun
See bug, apparently it's "an up-to-date thing" but "thing is up to date".
The bug is only about grd files, but I went through `git grep -l up-to-date`
while I was at it.
BUG=344535
TBR=IPC owner
CQ_INCLUDE_TRYBOTS=tryserver.chromium.linux:closure_compilation;tryserver.blink:linux_blink_rel
Review-Url: https://codereview.chromium.org/2059143002
Cr-Original-Commit-Position: refs/heads/master@{#399698}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: 3e861deabe8e47db274ed779acc1a3b80837e16d
diff --git a/tools/gn/docs/reference.md b/tools/gn/docs/reference.md
index 4071fd9..70666b0 100644
--- a/tools/gn/docs/reference.md
+++ b/tools/gn/docs/reference.md
@@ -4686,7 +4686,7 @@
The problem happens if a file is ever removed because the inputs are
not listed on the command line to the script. Because the script
- hasn't changed and all inputs are up-to-date, the script will not
+ hasn't changed and all inputs are up to date, the script will not
re-run and you will get a stale build. Instead, either list all
inputs on the command line to the script, or if there are many, create
a separate list file that the script reads. As long as this file is
@@ -4704,7 +4704,7 @@
you do not typically need to list them in the inputs section.
Inputs for binary targets will be treated as order-only dependencies,
- meaning that they will be forced up-to-date before compiling or
+ meaning that they will be forced up to date before compiling or
any files in the target, but changes in the inputs will not
necessarily force the target to compile. This is because it is
expected that the compiler will report the precise list of input
diff --git a/tools/gn/ninja_action_target_writer.cc b/tools/gn/ninja_action_target_writer.cc
index aed8ffb..1743632 100644
--- a/tools/gn/ninja_action_target_writer.cc
+++ b/tools/gn/ninja_action_target_writer.cc
@@ -166,7 +166,7 @@
path_output_.WriteFile(out_, sources[i]);
if (!input_dep.value().empty()) {
// Using "|" for the dependencies forces all implicit dependencies to be
- // fully up-to-date before running the action, and will re-run this
+ // fully up to date before running the action, and will re-run this
// action if any input dependencies change. This is important because
// this action may consume the outputs of previous steps.
out_ << " | ";
diff --git a/tools/gn/ninja_binary_target_writer.cc b/tools/gn/ninja_binary_target_writer.cc
index 30658f2..b012e42 100644
--- a/tools/gn/ninja_binary_target_writer.cc
+++ b/tools/gn/ninja_binary_target_writer.cc
@@ -271,7 +271,7 @@
WriteCompilerVars(used_types);
// The input dependencies will be an order-only dependency. This will cause
- // Ninja to make sure the inputs are up-to-date before compiling this source,
+ // Ninja to make sure the inputs are up to date before compiling this source,
// but changes in the inputs deps won't cause the file to be recompiled.
//
// This is important to prevent changes in unrelated actions that are
diff --git a/tools/gn/variables.cc b/tools/gn/variables.cc
index 8bafb68..210eb5d 100644
--- a/tools/gn/variables.cc
+++ b/tools/gn/variables.cc
@@ -986,7 +986,7 @@
"\n"
" The problem happens if a file is ever removed because the inputs are\n"
" not listed on the command line to the script. Because the script\n"
- " hasn't changed and all inputs are up-to-date, the script will not\n"
+ " hasn't changed and all inputs are up to date, the script will not\n"
" re-run and you will get a stale build. Instead, either list all\n"
" inputs on the command line to the script, or if there are many, create\n"
" a separate list file that the script reads. As long as this file is\n"
@@ -1001,7 +1001,7 @@
" you do not typically need to list them in the inputs section.\n"
"\n"
" Inputs for binary targets will be treated as order-only dependencies,\n"
- " meaning that they will be forced up-to-date before compiling or\n"
+ " meaning that they will be forced up to date before compiling or\n"
" any files in the target, but changes in the inputs will not\n"
" necessarily force the target to compile. This is because it is\n"
" expected that the compiler will report the precise list of input\n"
