Skip to content

Commit

Permalink
Remove spurious colon in git push command
Browse files Browse the repository at this point in the history
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 Mar 4, 2011
1 parent b005bb9 commit 435c9ed
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion _posts/2009-02-03-tagging.textile
Expand Up @@ -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!

Expand Down

0 comments on commit 435c9ed

Please sign in to comment.