git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: git@vger.kernel.org, Jeff King <peff@peff.net>
Subject: Re: [PATCH] doc: doc-diff: specify date
Date: Thu, 04 May 2023 18:15:59 -0700	[thread overview]
Message-ID: <xmqq8re3inn4.fsf@gitster.g> (raw)
In-Reply-To: <20230503232349.59997-1-felipe.contreras@gmail.com> (Felipe Contreras's message of "Wed, 3 May 2023 17:23:49 -0600")

Felipe Contreras <felipe.contreras@gmail.com> writes:

> Otherwise comparing the output of commits with different dates generates
> unnecessary diffs.
>
> Signed-off-by: Felipe Contreras <felipe.contreras@gmail.com>
> ---
>  Documentation/doc-diff | 1 +
>  1 file changed, 1 insertion(+)

Ahh, it is a fix for a fallout from 28fde3a1 (doc: set actual
revdate for manpages, 2023-04-13); when it is shown in the patch
form like this, it is kind of obvious why we need to compensate for
that change this way, but apparently "doc-diff" slipped everybody's
mind back then when we were looking at the change.

Looking at the patch text of 28fde3a1, we pass GIT_VERSION and
GIT_DATE to AsciiDoc since that version.  We were already covering
GIT_VERSION by hardcoded "omitted" string, and now we compensate for
the other one here, which means this change and the other changes
complement each other, and there shouldn't be a need to further
adjustment for that change around this area.  Looking good.

> diff --git a/Documentation/doc-diff b/Documentation/doc-diff
> index 1694300e50..554a78a12d 100755
> --- a/Documentation/doc-diff
> +++ b/Documentation/doc-diff
> @@ -153,6 +153,7 @@ render_tree () {
>  		make -j$parallel -C "$tmp/worktree" \
>  			$makemanflags \
>  			GIT_VERSION=omitted \
> +			GIT_DATE=1970-01-01 \
>  			SOURCE_DATE_EPOCH=0 \
>  			DESTDIR="$tmp/installed/$dname+" \
>  			install-man &&

I wonder what the existing SOURCE_DATE_EPOCH was trying to do there,
though.

Will queue.  Thanks.

  reply	other threads:[~2023-05-05  1:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-03 23:23 [PATCH] doc: doc-diff: specify date Felipe Contreras
2023-05-05  1:15 ` Junio C Hamano [this message]
2023-05-05  1:46   ` Jeff King
2023-05-05  5:55     ` Junio C Hamano
2023-05-05 21:16       ` Jeff King
2023-05-08  2:08   ` Felipe Contreras

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=xmqq8re3inn4.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=felipe.contreras@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    /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).