Autogenerated HTML docs for v1.5.3.4-319-gdd817

1 files changed, 17 insertions, 2 deletions

diff --git a/git-tag.html b/git-tag.html
index 821945167..fabdaea08 100644
--- a/git-tag.html
+++ b/git-tag.html
@@ -426,7 +426,7 @@ again, as if you hadn't already published the old one.
 </p>

 </li>

 </ol>

-<p>However, Git does <strong>not</strong> (and it should not)change tags behind

+<p>However, Git does <strong>not</strong> (and it should not) change tags behind

 users back. So if somebody already got the old tag, doing a "git

 pull" on your tree shouldn't just make them overwrite the old

 one.</p>

@@ -513,6 +513,21 @@ exchange the tags internal to their group, but in that workflow
 they are most likely tracking with each other's progress by

 having tracking branches.  Again, the heuristic to automatically

 follow such tags is a good thing.</p>

+<h3>On Backdating Tags</h3>

+<p>If you have imported some changes from another VCS and would like

+to add tags for major releases of your work, it is useful to be able

+to specify the date to embed inside of the tag object.  The data in

+the tag object affects, for example, the ordering of tags in the

+gitweb interface.</p>

+<p>To set the date used in future tag objects, set the environment

+variable GIT_AUTHOR_DATE to one or more of the date and time.  The

+date and time can be specified in a number of ways; the most common

+is "YYYY-MM-DD HH:MM".</p>

+<p>An example follows.</p>

+<div class="listingblock">

+<div class="content">

+<pre><tt>$ GIT_AUTHOR_DATE="2006-10-02 10:31" git tag -s v1.0.1</tt></pre>

+</div></div>

 </div>

 <h2>Author</h2>

 <div class="sectionbody">

@@ -529,7 +544,7 @@ Junio C Hamano &lt;junkio@cox.net&gt; and Chris Wright &lt;chrisw@osdl.org&gt;.<
 </div>

 <div id="footer">

 <div id="footer-text">

-Last updated 28-Aug-2007 06:25:09 UTC

+Last updated 23-Oct-2007 01:22:00 UTC

 </div>

 </div>

 </body>