gergely/git-reference
1
0
Fork 0
Code Releases Activity

Note difference on default behaviour on fetch/push on repo tags

Browse Source
This commit is contained in:
Soon Van 2012-12-18 18:51:24 -05:00
parent 690a441c25
commit dbdd946cd9
1 changed files with 10 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
branching/index.html
View File

@ -774,10 +774,11 @@ ab5ab4c added erlang
* 17f4acf first commit * 17f4acf first commit
</pre> </pre>
<p>By default, tags are not included when you <code>push</code> to or <p>Tags pointing to objects tracked from branch heads will be
<code>fetch</code> from a remote repository. In order to explicitly automatically downloaded when you <code>fetch</code> from a remote
update these you must include the <code>--tags</code> option to transfer repository. However, tags that aren't reachable from branch heads
all the tags on the repo. will be skipped. If you want to make sure <em>all</em> tags are <em>always</em>
included, you must include the <code>--tags</code> option.
</p> </p>
<pre> <pre>
@ -796,6 +797,11 @@ From git://github.com:example-user/example-repo
<code>git fetch &lt;remote> tag &lt;tag-name></code>. <code>git fetch &lt;remote> tag &lt;tag-name></code>.
</p> </p>
<p>By default, tags are not included when you <code>push</code> to
a remote repository. In order to explicitly update these you must
include the <code>--tags</code> option when using <code>git push</code>.
</p>
<p class="nutshell"> <p class="nutshell">
<b>In a nutshell</b> you use <code>git tag</code> to mark a <b>In a nutshell</b> you use <code>git tag</code> to mark a
commit or point in your repo as important. This also allows commit or point in your repo as important. This also allows