Permalink
Browse files

Remove spurious colon in git push command

With the colon, this command will push not only the tag, but also all
local branches matching remote ones (c.f. end of the refspec section in
the git push manual).
  • Loading branch information...
priteau committed Jan 18, 2011
1 parent b005bb9 commit 435c9ed5292248bbb8026afbc0b842f5d68e1d78
Showing with 1 addition and 1 deletion.
  1. +1 −1 _posts/2009-02-03-tagging.textile
@@ -54,7 +54,7 @@ $ git push --tags
* [new tag] v1.0.0 -> v1.0.0
</pre>
-The second describe command shows us that we're one commit ahead of where the last tag was done. This is an easy way to figure out how much work has been done since the last commit. Also, the @--tags@ option was used to push here, but just the one tag could have been pushed with @git push origin : v1.0.0@. On GitHub (or on your remote) you should see the tag pushed up:
+The second describe command shows us that we're one commit ahead of where the last tag was done. This is an easy way to figure out how much work has been done since the last commit. Also, the @--tags@ option was used to push here, but just the one tag could have been pushed with @git push origin v1.0.0@. On GitHub (or on your remote) you should see the tag pushed up:
p=. !/images/tag.png!

0 comments on commit 435c9ed

Please sign in to comment.