public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Michael Olson <mwolson@gnu•org>
To: Junio C Hamano <gitster@pobox•com>, git@vger•kernel.org
Subject: [PATCH] Documentation/git-tag.txt: Document how to backdate tags
Date: Mon, 15 Oct 2007 13:51:30 -0400	[thread overview]
Message-ID: <87lka4cllp.fsf@hariken.mwolson.org> (raw)
In-Reply-To: <7vd4w0iqd5.fsf@gitster.siamese.dyndns.org> (Junio C. Hamano's message of "Sun, 30 Sep 2007 00:06:46 -0700")

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.

Signed-off-by: Michael W. Olson <mwolson@gnu•org>
---

[Resending, this time without trying to send through Gmane and munge
Reply-To.]

Junio C Hamano <gitster@pobox•com> writes:

> Michael Olson <mwolson@gnu•org> writes:
>
>> Junio C Hamano <gitster@pobox•com> writes:
>>
>>> Wouldn't it be easier to create the tag with the desired
>>> timestamp from the beginning, by exporting GIT_COMMITTER_DATE?
>>
>> Ah, I didn't know about that environment variable.
>>
>> Would it be possible to mention that option on the git-tag manpage?
>
> Surely, I am kind of surprised if it weren't, but apparently you
> did not find it.  Please make it so.

 Documentation/git-tag.txt |   21 +++++++++++++++++++++
 1 files changed, 21 insertions(+), 0 deletions(-)

diff --git a/Documentation/git-tag.txt b/Documentation/git-tag.txt
index 990ae4f..2966aa2 100644
--- a/Documentation/git-tag.txt
+++ b/Documentation/git-tag.txt
@@ -214,6 +214,27 @@ having tracking branches.  Again, the heuristic to automatically
 follow such tags is a good thing.
 
 
+On Backdating Tags
+~~~~~~~~~~~~~~~~~~
+
+If you have imported some changes from another VCS and would like
+to add tags for major releases of you 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.
+
+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".
+
+An example follows.
+
+------------
+$ GIT_AUTHOR_DATE="2006-10-02 10:31" git tag -s v1.0.1
+------------
+
+
 Author
 ------
 Written by Linus Torvalds <torvalds@osdl•org>,
-- 
1.5.3.4

  parent reply	other threads:[~2007-10-15 18:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-30  3:16 Script to backdate tags Michael Olson
2007-09-30  4:29 ` Michael Olson
2007-09-30  5:16   ` Junio C Hamano
2007-09-30  6:27     ` Michael Olson
     [not found]       ` <7vd4w0iqd5.fsf@gitster.siamese.dyndns.org>
2007-10-15 17:51         ` Michael Olson [this message]
2007-10-15 20:35           ` [PATCH] Documentation/git-tag.txt: Document how " Jeff King
2007-10-15 22:53             ` Michael Olson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87lka4cllp.fsf@hariken.mwolson.org \
    --to=mwolson@gnu$(echo .)org \
    --cc=git@vger$(echo .)kernel.org \
    --cc=gitster@pobox$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox