git/list[1] front-page[2] threads[3] people[4] search[5] about
 

implement a stable 'Last updated' in Documentation

From
Olaf Hering <olaf@aepfle.de>
Date
Jan 26, 2015, 17:24 UTC
Message-ID
<20150126172409.GA15204@aepfle.de>

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: Olaf Hering
Message 1 of 11 in “implement a stable 'Last updated' in Documentation”
  1. Olaf HeringJan 26, 2015
  2. Olaf HeringJan 27, 2015
  3. Junio C HamanoJan 27, 2015
  4. Olaf HeringJan 28, 2015
  5. Junio C HamanoJan 29, 2015
  6. Michael J GruberJan 30, 2015
  7. Jeff KingJan 30, 2015
  8. Olaf HeringFeb 10, 2015
  9. Jeff KingFeb 10, 2015
  10. Olaf HeringSep 1, 2016
  11. Jeff KingSep 1, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.