From: Salvatore Bonaccorso <carnil@debian.org>
To: Ben Hutchings <ben@decadent.org.uk>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf tools: Use $KBUILD_BUILD_TIMESTAMP as man page date
Date: Tue, 9 May 2023 21:03:28 +0200 [thread overview]
Message-ID: <ZFqZAB2ZShmdKtvy@eldamar.lan> (raw)
In-Reply-To: <20160517132809.GE7555@decadent.org.uk>
Hi Peter, Ingo, Arnaldo,
On Tue, May 17, 2016 at 02:28:09PM +0100, Ben Hutchings wrote:
> This allows man pages to be built reproducibly.
>
> Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
> ---
> --- a/tools/perf/Documentation/Makefile
> +++ b/tools/perf/Documentation/Makefile
> @@ -120,6 +120,9 @@ endif
> ifdef DOCBOOK_SUPPRESS_SP
> XMLTO_EXTRA += -m manpage-suppress-sp.xsl
> endif
> +ifdef KBUILD_BUILD_TIMESTAMP
> +ASCIIDOC_EXTRA += -a revdate=$(shell date -u -d '$(KBUILD_BUILD_TIMESTAMP)' +%Y-%m-%d)
> +endif
>
> SHELL_PATH ?= $(SHELL)
> # Shell quote;
> --- a/tools/perf/Documentation/asciidoc.conf
> +++ b/tools/perf/Documentation/asciidoc.conf
> @@ -71,6 +71,9 @@ ifdef::backend-docbook[]
> [header]
> template::[header-declarations]
> <refentry>
> +<refentryinfo>
> +template::[docinfo]
> +</refentryinfo>
> <refmeta>
> <refentrytitle>{mantitle}</refentrytitle>
> <manvolnum>{manvolnum}</manvolnum>
As we do apply the change in Downstream in Debian, I was wondering if
it just felt trough the cracks and could still be applied. Is there
anything missing?
Regards,
Salvatore
next prev parent reply other threads:[~2023-05-09 19:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-17 13:28 [PATCH] perf tools: Use $KBUILD_BUILD_TIMESTAMP as man page date Ben Hutchings
2023-05-09 19:03 ` Salvatore Bonaccorso [this message]
2023-05-10 12:59 ` Arnaldo Carvalho de Melo
2023-05-13 18:51 ` Ben Hutchings
2023-05-13 19:33 ` Ben Hutchings
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=ZFqZAB2ZShmdKtvy@eldamar.lan \
--to=carnil@debian.org \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=ben@decadent.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.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