Fix link to PR

ajkannan · ajkannan · commit c1d1fb724630 · 2015-10-09T16:26:24.000-07:00
diff --git a/RELEASING.md b/RELEASING.md
@@ -24,4 +24,4 @@ Pushing a snapshot is completely automated.  If "-SNAPSHOT" is included in the v
 
 ### Improvements
 
-Automatic tagging is not currently implemented, though it was discussed in #119.  If the version updates continue to be manual, a one-line git tag command can be added to `after_success.sh` to correctly tag releases.  However, automatically creating useful annotations for this tag will be difficult.  Also, if the release process becomes fully automated, tagging becomes a harder problem, as mentioned in that issue.
+Automatic tagging is not currently implemented, though it was discussed in [#119](https://github.com/GoogleCloudPlatform/gcloud-java/pull/119).  If the version updates continue to be manual, a one-line git tag command can be added to `after_success.sh` to correctly tag releases.  However, automatically creating useful annotations for this tag will be difficult.  Also, if the release process becomes fully automated, tagging becomes a harder problem, as mentioned in that issue.

Original file line number	Diff line number	Diff line change
`@@ -24,4 +24,4 @@ Pushing a snapshot is completely automated. If "-SNAPSHOT" is included in the v`
`24`	`24`
`25`	`25`	`### Improvements`
`26`	`26`
`27`		-Automatic tagging is not currently implemented, though it was discussed in #119. If the version updates continue to be manual, a one-line git tag command can be added to `after_success.sh` to correctly tag releases. However, automatically creating useful annotations for this tag will be difficult. Also, if the release process becomes fully automated, tagging becomes a harder problem, as mentioned in that issue.
	`27`	+Automatic tagging is not currently implemented, though it was discussed in [#119](https://github.com/GoogleCloudPlatform/gcloud-java/pull/119). If the version updates continue to be manual, a one-line git tag command can be added to `after_success.sh` to correctly tag releases. However, automatically creating useful annotations for this tag will be difficult. Also, if the release process becomes fully automated, tagging becomes a harder problem, as mentioned in that issue.