Re: implement a stable 'Last updated' in Documentation

2016-09-01 Thread Jeff King
On Thu, Sep 01, 2016 at 04:37:36PM +0200, Olaf Hering wrote: > Hey, asciidoc made a move, so this patch is good to go: > https://github.com/asciidoc/asciidoc/pull/9 Sine this thread is 18 months old, I needed some recap to remember what we were talking about. :) It's here:

Re: implement a stable 'Last updated' in Documentation

2016-09-01 Thread Olaf Hering
Hey, asciidoc made a move, so this patch is good to go: https://github.com/asciidoc/asciidoc/pull/9 Thanks. Olaf On Tue, Feb 10, Jeff King wrote: > On Tue, Feb 10, 2015 at 04:17:47PM +0100, Olaf Hering wrote: > > > On Fri, Jan 30, Jeff King wrote: > > > > > I have 8.6.9-3 installed (it is

Re: implement a stable 'Last updated' in Documentation

2015-02-10 Thread Olaf Hering
On Fri, Jan 30, Jeff King wrote: I have 8.6.9-3 installed (it is part of Debian testing/unstable now), and confirmed that: diff --git a/Documentation/asciidoc.conf b/Documentation/asciidoc.conf index 2c16c53..10c777e 100644 --- a/Documentation/asciidoc.conf +++

Re: implement a stable 'Last updated' in Documentation

2015-02-10 Thread Jeff King
On Tue, Feb 10, 2015 at 04:17:47PM +0100, Olaf Hering wrote: On Fri, Jan 30, Jeff King wrote: I have 8.6.9-3 installed (it is part of Debian testing/unstable now), and confirmed that: diff --git a/Documentation/asciidoc.conf b/Documentation/asciidoc.conf index 2c16c53..10c777e

Re: implement a stable 'Last updated' in Documentation

2015-01-30 Thread Jeff King
On Fri, Jan 30, 2015 at 11:05:36AM +0100, Michael J Gruber wrote: 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

Re: implement a stable 'Last updated' in Documentation

2015-01-30 Thread Michael J Gruber
Junio C Hamano schrieb am 29.01.2015 um 07:18: Olaf Hering o...@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

Re: implement a stable 'Last updated' in Documentation

2015-01-28 Thread Olaf Hering
On Tue, Jan 27, Junio C Hamano wrote: Olaf Hering o...@aepfle.de writes: 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:

Re: implement a stable 'Last updated' in Documentation

2015-01-28 Thread Junio C Hamano
Olaf Hering o...@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

Re: implement a stable 'Last updated' in Documentation

2015-01-27 Thread Junio C Hamano
Olaf Hering o...@aepfle.de writes: 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

Re: implement a stable 'Last updated' in Documentation

2015-01-27 Thread Olaf Hering
On Mon, Jan 26, Olaf Hering wrote: 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

implement a stable 'Last updated' in Documentation

2015-01-26 Thread Olaf Hering
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