From: Michael J Gruber <git@drmicha.warpmail.net>
To: Junio C Hamano <gitster@pobox.com>, Olaf Hering <olaf@aepfle.de>
Cc: git@vger.kernel.org
Subject: Re: implement a stable 'Last updated' in Documentation
Date: Fri, 30 Jan 2015 11:05:36 +0100 [thread overview]
Message-ID: <54CB5770.8030503@drmicha.warpmail.net> (raw)
In-Reply-To: <xmqqbnlif6t9.fsf@gitster.dls.corp.google.com>
Junio C Hamano schrieb am 29.01.2015 um 07:18:
> Olaf Hering <olaf@aepfle.de> writes:
>
>> On Tue, Jan 27, Junio C Hamano wrote:
>>
>>>> What file timestamp should be used for them? Likely "../version"?
>>>
>>> I tend to think the "Last updated" timestamp taken from the
>>> filesystem timestamp is a bad practice inherited by these tools from
>>> the days back when nobody used any revision control systems.
>>
>> I'm not sure. The bug is that such 'Last updated' line exists at all in
>> the default output. Noone asked for it, noone really needs it. And it
>> makes it impossible to get reproducible builds.
>
> Amen to that ;-)
>
It's a shame one can't simply replace the [footer-text] template which
asciidoc insists on.
It turns out asciidoc 8.6.9-3 and later will habe a knob to turn:
https://github.com/asciidoc/asciidoc/pull/9
I'll try and get my hands on it to see whether we can simply use that.
I'm wondering though which is more useful - the version of the tree the
doc is processed from, or the version of the last commit changing the
corresponding doc source file. The first one changes even when the doc
source is unchanged (but is stable between reruns, of course).
Michael
next prev parent reply other threads:[~2015-01-30 10:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-26 17:24 implement a stable 'Last updated' in Documentation Olaf Hering
2015-01-27 11:11 ` Olaf Hering
2015-01-27 23:10 ` Junio C Hamano
2015-01-28 8:02 ` Olaf Hering
2015-01-29 6:18 ` Junio C Hamano
2015-01-30 10:05 ` Michael J Gruber [this message]
2015-01-30 15:07 ` Jeff King
2015-02-10 15:17 ` Olaf Hering
2015-02-10 18:43 ` Jeff King
2016-09-01 14:37 ` Olaf Hering
2016-09-01 20:17 ` Jeff King
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=54CB5770.8030503@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=olaf@aepfle.de \
/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).