Skip to content

Commit 5040bef

Browse files
mwolsonspearce
authored andcommitted
Documentation/git-tag.txt: Document how to backdate tags
Added a new section beneath "On Automatic following" called "On Backdating Tags". This includes an explanation of when to use this method, a brief explanation of the kind of date that can be used in GIT_AUTHOR_DATE, and an example invocation of git-tag using a custom setting of GIT_AUTHOR_DATE. [sp: Corrected s/you/your/, noticed by Jeff King] Signed-off-by: Michael W. Olson <[email protected]> Signed-off-by: Shawn O. Pearce <[email protected]>
1 parent 2858028 commit 5040bef

File tree

1 file changed

+21
-0
lines changed

1 file changed

+21
-0
lines changed

Documentation/git-tag.txt

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -214,6 +214,27 @@ having tracking branches. Again, the heuristic to automatically
214214
follow such tags is a good thing.
215215

216216

217+
On Backdating Tags
218+
~~~~~~~~~~~~~~~~~~
219+
220+
If you have imported some changes from another VCS and would like
221+
to add tags for major releases of your work, it is useful to be able
222+
to specify the date to embed inside of the tag object. The data in
223+
the tag object affects, for example, the ordering of tags in the
224+
gitweb interface.
225+
226+
To set the date used in future tag objects, set the environment
227+
variable GIT_AUTHOR_DATE to one or more of the date and time. The
228+
date and time can be specified in a number of ways; the most common
229+
is "YYYY-MM-DD HH:MM".
230+
231+
An example follows.
232+
233+
------------
234+
$ GIT_AUTHOR_DATE="2006-10-02 10:31" git tag -s v1.0.1
235+
------------
236+
237+
217238
Author
218239
------
219240
Written by Linus Torvalds <[email protected]>,

0 commit comments

Comments
 (0)