From: Olaf Hering <olaf@aepfle.de>
To: git@vger.kernel.org
Subject: implement a stable 'Last updated' in Documentation
Date: Mon, 26 Jan 2015 18:24:09 +0100 [thread overview]
Message-ID: <20150126172409.GA15204@aepfle.de> (raw)
Several files in Documentation have an unstable 'Last updated' timestamp. The
reason is that their mtime changes every time, which prevents reproducible
builds.
341 technical/api-index.txt: technical/api-index-skel.txt \
342 technical/api-index.sh $(patsubst %,%.txt,$(API_DOCS))
343 $(QUIET_GEN)cd technical && '$(SHELL_PATH_SQ)' ./api-index.sh
388 howto-index.txt: howto-index.sh $(wildcard howto/*.txt)
389 $(QUIET_GEN)$(RM) $@+ $@ && \
390 '$(SHELL_PATH_SQ)' ./howto-index.sh $(sort $(wildcard howto/*.txt)) >$@+ && \
391 mv $@+ $@
399 $(patsubst %.txt,%.html,$(wildcard howto/*.txt)): %.html : %.txt
400 $(QUIET_ASCIIDOC)$(RM) $@+ $@ && \
401 sed -e '1,/^$$/d' $< | \
402 $(TXT_TO_HTML) - >$@+ && \
403 mv $@+ $@
What file timestamp should be used for them? Likely "../version"?
The final file, before passing it to asciidoc, should get a fixed timestamp
with 'touch -r $reference_file $file'.
Olaf
next reply other threads:[~2015-01-26 17:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-26 17:24 Olaf Hering [this message]
2015-01-27 11:11 ` implement a stable 'Last updated' in Documentation 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
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=20150126172409.GA15204@aepfle.de \
--to=olaf@aepfle.de \
--cc=git@vger.kernel.org \
/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).