anchor.diff:      command: my-go-server
   ```
   
  -If you do not specify a start command via a `Procfile`, in the manifest, or via the `-c` flag for `cf push`, the generated binary will be used as the start command. (ex. `my-go-server`)
  +If you do not specify a start command in a `Procfile`, in the manifest, or with the `-c` flag for `cf push`, the generated binary will be used as the start command. Example: `my-go-server`
   
   ### <a id='with_godep'></a>Push an App with godep ###
   If you are using [godep](https://github.com/tools/godep) to package your dependencies, make sure that you have created a valid `Godeps/Godeps.json` file in the root directory of your app by running `godep save`.
  
positive.code: #### <a id='go_1.6'></a>Go 1.6 ####
  * [Sample Go 1.6 app with native vendoring](https://github.com/cloudfoundry/go-buildpack/tree/develop/cf_spec/fixtures/go_with_native_vendoring/src/go_app).
  
  Go 1.6 has vendoring turned on by default. You can turn it off by setting `GO15VENDOREXPERIMENT=0`.
  
  An example `manifest.yml`:
  
  ```yaml
  ---
  
negative.code: ```
  
  #### <a id='go 1.5'></a>Go 1.5 ####
  <p class='note'><strong>NOTE/strong>: For Go 1.5, native vendoring is disabled by default. You must set the <code>GO15VENDOREXPERIMENT</code> environment variable to <code>1</code> in your <code>manifest.yml</code> file to use this native vendoring.</p>
  
  If you use the `vendor/` directory for dependencies, you can set the Go version with the `GOVERSION` environment variable.
  
  An example `manifest.yml` file:
  
  ```yaml
  ---
  