From: Jeff King <peff@peff.net>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: Junio C Hamano <gitster@pobox.com>, Olaf Hering <olaf@aepfle.de>,
git@vger.kernel.org
Subject: Re: implement a stable 'Last updated' in Documentation
Date: Fri, 30 Jan 2015 10:07:58 -0500 [thread overview]
Message-ID: <20150130150758.GA3683@peff.net> (raw)
In-Reply-To: <54CB5770.8030503@drmicha.warpmail.net>
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 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).
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
+++ b/Documentation/asciidoc.conf
@@ -21,6 +21,7 @@ tilde=~
apostrophe='
backtick=`
litdd=--
+footer-style=none
ifdef::backend-docbook[]
[linkgit-inlinemacro]
drops the "last-updated" footer.
But note that this only affects the generated HTML. The manpages still
get the date in their footer. But this isn't an asciidoc-ism at all;
it's added by docbook when converting the xml to roff. I'm sure there is
a way to tweak that, too, but looking at docbook gives me nightmares.
-Peff
next prev parent reply other threads:[~2015-01-30 15:08 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
2015-01-30 15:07 ` Jeff King [this message]
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=20150130150758.GA3683@peff.net \
--to=peff@peff.net \
--cc=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).