git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Kalle Olavi Niemitalo <kon@iki.fi>
Cc: git@vger.kernel.org
Subject: Re: [DOC BUG] git tag uses GIT_COMMITTER_DATE, not GIT_AUTHOR_DATE
Date: Mon, 11 Feb 2008 01:09:27 -0800	[thread overview]
Message-ID: <7vir0vamgo.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <87ir0vc2gw.fsf@Astalo.kon.iki.fi> (Kalle Olavi Niemitalo's message of "Mon, 11 Feb 2008 10:38:23 +0200")

Kalle Olavi Niemitalo <kon@iki.fi> writes:

> In Git v1.5.4.1, Documentation/git-tag.txt advises:
>
>> 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".
>
> But this does not work because git tag uses GIT_COMMITTER_DATE instead.
> In builtin-tag.c:
>
>> 	header_len = snprintf(header_buf, sizeof(header_buf),
>> 			  "object %s\n"
>> 			  "type %s\n"
>> 			  "tag %s\n"
>> 			  "tagger %s\n\n",
>> 			  sha1_to_hex(object),
>> 			  typename(type),
>> 			  tag,
>> 			  git_committer_info(IDENT_ERROR_ON_NO_NAME));
>
> i.e. it does not call git_author_info.
>
> The backdating section was added to git-tag.txt in 5040beff,
> and builtin-tag.c already used git_committer_info at that time.
> The older git-tag.sh used tagger=$(git-var GIT_COMMITTER_IDENT).
> Thus it seems the bug is in the documentation, not in the code.

Correct.  We've always used committer ident as far as I can
remember.

      reply	other threads:[~2008-02-11  9:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-11  8:38 [DOC BUG] git tag uses GIT_COMMITTER_DATE, not GIT_AUTHOR_DATE Kalle Olavi Niemitalo
2008-02-11  9:09 ` Junio C Hamano [this message]

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=7vir0vamgo.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=kon@iki.fi \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).