From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Ben Hutchings <ben@decadent.org.uk>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
linux-perf-users <linux-perf-users@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Salvatore Bonaccorso <carnil@debian.org>
Subject: Re: [PATCH v2 0/2] perf doc improvements to man page reproducibility
Date: Mon, 15 May 2023 17:49:19 -0300 [thread overview]
Message-ID: <ZGKaz/wrobQGJAqk@kernel.org> (raw)
In-Reply-To: <CAP-5=fXmL509c2rhE7SYj9FW62eZPc7tPEWzG1h0DztF+Qmnww@mail.gmail.com>
Em Mon, May 15, 2023 at 07:26:52AM -0700, Ian Rogers escreveu:
> On Sat, May 13, 2023, 1:35 PM Ben Hutchings <ben@decadent.org.uk> wrote:
>
> > I previously sent a patch in 2016(!) to make the dates in man pages
> > reproducible, with KBUILD_BUILD_TIMESTAMP specifiying the date. That
> > patch partly overlaps with commit d586ac10ce56 "perf docs: Allow man
> > page date to be specified", which implemented generation of dates
> > based on commit timestamps.
> >
> > However, both of those implementations were specific to the original
> > asciidoc's DocBook backend and had no effect on asciidoctor's direct
> > man page generation.
> >
> > This series builds on the current definition of perf_date, adding
> > support for asciidoctor and the KBUILD_BUILD_TIMESTAMP variable.
> >
> > Ben.
> >
> > Ben Hutchings (2):
> > perf doc: Define man page date when using asciidoctor
> > perf doc: Add support for KBUILD_BUILD_TIMESTAMP
> >
>
> Acked-by: Ian Rogers<irogers@google.com>
Thanks, applied.
- Arnaldo
prev parent reply other threads:[~2023-05-15 20:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-13 20:35 [PATCH v2 0/2] perf doc improvements to man page reproducibility Ben Hutchings
2023-05-13 20:37 ` [PATCH v2 1/2] perf doc: Define man page date when using asciidoctor Ben Hutchings
2023-05-13 20:37 ` [PATCH v2 2/2] perf doc: Add support for KBUILD_BUILD_TIMESTAMP Ben Hutchings
[not found] ` <CAP-5=fXmL509c2rhE7SYj9FW62eZPc7tPEWzG1h0DztF+Qmnww@mail.gmail.com>
2023-05-15 20:49 ` Arnaldo Carvalho de Melo [this message]
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=ZGKaz/wrobQGJAqk@kernel.org \
--to=acme@kernel.org \
--cc=ben@decadent.org.uk \
--cc=carnil@debian.org \
--cc=irogers@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@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;
as well as URLs for NNTP newsgroup(s).