gn desc: printing public_deps without --all and --tree

tools/gn/command_desc.cc

Index: tools/gn/command_desc.cc
diff --git a/tools/gn/command_desc.cc b/tools/gn/command_desc.cc
index 8dbe6de7de932ec9b67c7cf2219cc6acbf6b8293..37e3ef2bb5f056afd453fc948fb9f1bf05814408 100644
--- a/tools/gn/command_desc.cc
+++ b/tools/gn/command_desc.cc
@@ -314,6 +314,7 @@ Possibilities for <what to show>
   cflags_cxx [--blame]
   check_includes
   configs [--tree] (see below)
+  data_deps (see below)
   defines [--blame]
   depfile
   deps [--all] [--tree] (see below)
@@ -322,9 +323,11 @@ Possibilities for <what to show>
   ldflags [--blame]
   lib_dirs
   libs
+  linked_deps (see below)
   outputs
-  public_configs
   public
+  public_configs
+  public_deps (see below)
   script
   sources
   testonly
@@ -372,8 +375,17 @@ Printing outputs
 
 Printing deps
 
-  Deps will include all public, private, and data deps (TODO this could be
-  clarified and enhanced) sorted in order applying. The following may be used:
+  There are 4 different fields which contain information about deps:
+
+    - deps: if the command is invoked without --tree and --all it just

[brettw, 2017/06/08 18:02:52]

The formatting I would use in other places to avoid ambiguity with hyphen being
for command line flags is a separate line for the heading, and then a 4-space
indent with complete sentences:

    deps
        If the command is invoked...
    public_deps
        If the...

[mbonadei1, 2017/06/09 11:16:36]

Done.

+        includes private deps (see below for --tree and --all);
+    - public_deps: if the command is invoked without --tree and --all it
+        includes public deps. If the command is invoked with --tree or --all
+        this field is not printed;
+    - data_deps: includes data deps;
+    - linked_deps: includes public and private deps sorted in order applying.
+
+  The following may be used:
 
   --all
       Collects all recursive dependencies and prints a sorted flat list. Also