anchor.diff:  
   The included `bootstrap.sh` should hopefully produce a working `ninja`
   binary, by first blindly compiling all non-test files together then
  -re-building ninja using itself.
  +re-building Ninja using itself.
   
   Usage is currently just
   
  
positive.code: project, while `rule` statements describe how to generate the files
  along a given edge of the graph.
  
  Semantic differences from make
  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  
  * A rule may point at a path for extra implicit dependency
    information.  This makes it easy to get header dependencies correct
    for C/C++ code.
  
  
negative.code: 
  `command` (_required_):: the command line to run.
  
  `depfile`:: path to an optional `Makefile` that contains extra
    _implicit dependencies_ (see the <<ref_dependencies,the reference on
    dependency types>>).  The best example is how `gcc` has the `-M`
    family of flags to output the list of headers a given `.c` file
    depends on.
  +
  ----
  