anchor.diff:  
   When specifying versions, specify only major/minor versions, eg. go1.6, rather than go1.6.0. This will ensure you receive the most recent patches.
   
  -### <a id='start_command'></a>Start command ###
  +### <a id='start_command'></a>Start Command ###
   
   When pushing go apps, you can specify a start command for the app. The start command can be placed in the file `Procfile` in your app's root directory. For example, if the binary generated by your go project is `my-go-server`, your `Procfile` could be:
   
  
positive.code:   - foo
  ```
  
  ### <a id='pushing_Apps_with_native_Go_vendoring'></a>Pushing Apps with native Go vendoring ###
  If you are using the native Go vendoring system, which packages all local dependencies in the `vendor/` directory, you must specify your app's package name in the `GOPACKAGENAME` environment variable. An example `manifest.yml`:
  
  ```yaml
  
negative.code: 
  For an example usage, see the relevant [fixture app](https://github.com/cloudfoundry/go-buildpack/tree/develop/cf_spec/fixtures/go1.6_app_using_ldflags/src/go_app).
  
  ## <a id='c_dependencies'></a>C Dependencies ##
  
  This buildpack supports building with C dependencies via
  [cgo](https://golang.org/cmd/cgo/). You can set config vars to specify CGO flags
  