From dbdd946cd92bc13da11c6a80f6bb930731cd3702 Mon Sep 17 00:00:00 2001
From: Soon Van <cog@randomecho.com>
Date: Tue, 18 Dec 2012 18:51:24 -0500
Subject: [PATCH] Note difference on default behaviour on fetch/push on repo
 tags

---
 branching/index.html | 14 ++++++++++----
 1 file changed, 10 insertions(+), 4 deletions(-)

diff --git a/branching/index.html b/branching/index.html
index 6049a6a..8944dd8 100644
--- a/branching/index.html
+++ b/branching/index.html
@@ -774,10 +774,11 @@ ab5ab4c added erlang
 * 17f4acf first commit
 </pre>
 
-    <p>By default, tags are not included when you <code>push</code> to or
-      <code>fetch</code> from a remote repository. In order to explicitly
-      update these you must include the <code>--tags</code> option to transfer
-      all the tags on the repo.
+    <p>Tags pointing to objects tracked from branch heads will be
+      automatically downloaded when you <code>fetch</code> from a remote
+      repository. However, tags that aren't reachable from branch heads
+      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>
 
 <pre>
@@ -796,6 +797,11 @@ From git://github.com:example-user/example-repo
       <code>git fetch &lt;remote> tag &lt;tag-name></code>.
     </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">
     <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