aboutsummaryrefslogtreecommitdiffhomepage
path: root/src/main/java/com/google/devtools/build/lib/runtime
diff options
context:
space:
mode:
Diffstat (limited to 'src/main/java/com/google/devtools/build/lib/runtime')
-rw-r--r--src/main/java/com/google/devtools/build/lib/runtime/commands/target-syntax.txt9
1 files changed, 5 insertions, 4 deletions
diff --git a/src/main/java/com/google/devtools/build/lib/runtime/commands/target-syntax.txt b/src/main/java/com/google/devtools/build/lib/runtime/commands/target-syntax.txt
index 3eec42e21b..df0089bf8b 100644
--- a/src/main/java/com/google/devtools/build/lib/runtime/commands/target-syntax.txt
+++ b/src/main/java/com/google/devtools/build/lib/runtime/commands/target-syntax.txt
@@ -25,10 +25,11 @@ Specifying all rules recursively beneath a package:
//foo/...:all Matches all rules in all packages beneath directory 'foo'.
//foo/... (ditto)
- By default, directory symlinks are followed when performing this recursive
- traversal. But we understand that your workspace may intentionally contain
- directories with weird symlink structures that you don't want consumed. As
- such, if a directory has a file named
+ By default, directory symlinks are followed when performing this recursive traversal, except
+ those that point to under the output base (for example, the convenience symlinks that are created
+ in the root directory of the workspace) But we understand that your workspace may intentionally
+ contain directories with weird symlink structures that you don't want consumed. As such, if a
+ directory has a file named
'DONT_FOLLOW_SYMLINKS_WHEN_TRAVERSING_THIS_DIRECTORY_VIA_A_RECURSIVE_TARGET_PATTERN'
then symlinks in that directory won't be followed when evaluating recursive
target patterns.