Gary Yang <garyyang6@xxxxxxxxx> writes:
> I pushed code from my local repository to Git Server.
> git push git.company.com:/pub/git/training.git
>
> I, then tagged my local repository.
> git tag -u gyang@xxxxxxxxxxx RELEASE_2
git-push(1) manual page says that the syntax of the command is:
'git push' [--all | --mirror] [--dry-run] [--tags] [--receive-pack=<git-receive-pack>]
[--repo=<repository>] [-f | --force] [-v | --verbose]
[<repository> <refspec>...]
and its OPTIONS section explains what <refspec> means.
<refspec>...::
The canonical format of a <refspec> parameter is
`+?<src>:<dst>`; that is, an optional plus `{plus}`, followed
by the source ref, followed by a colon `:`, followed by
the destination ref.
...
The <src> side represents the source branch (or arbitrary
"SHA1 expression", such as `master~4` (four parents before the
tip of `master` branch); see linkgit:git-rev-parse[1]) that you
want to push. The <dst> side represents the destination location.
You want to update refs/tags/RELEASE_2 on the destination side (i.e. the
public server) with the same refs/tags/RELEASE_2 on the source side
(i.e. your side), so you would want to say
refs/tags/RELEASE_2:refs/tags/RELEASE_2
for <refspec>. The documentation further mentions that there is a
short-hand for that:
`tag <tag>` means the same as `refs/tags/<tag>:refs/tags/<tag>`.
Hence the command line becomes:
$ git push svdcgit01.amcc.com:/pub/git/training.git tag RELEASE_2
Note that saying "tag" is redundant these days as long as you do not have
a branch named "RELEASE_2" at the same time. But saying "tag" never
hurts, as it is still (and will be) supported.
Note to people who teach git to new people. The moral of the story is not
that people should learn to read the manual pages. It is that people
should not learn "push" without remote nor refspec first. In other words,
the first push command you teach them should be the "git push $over_there
$this_refspec" form, fully spelled.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
