From: Steven Rostedt <rostedt@goodmis.org>
To: Giulio Benetti <giulio.benetti@benettiengineering.com>
Cc: linux-trace-devel@vger.kernel.org
Subject: Re: [PATCH] libtraceevent: add option to disable documentation
Date: Sat, 30 Sep 2023 16:39:00 -0400 [thread overview]
Message-ID: <20230930163900.152d49fd@rorschach.local.home> (raw)
In-Reply-To: <ce8cac08-58be-4221-b5ab-fde7f9aab2bd@benettiengineering.com>
On Sat, 30 Sep 2023 22:32:52 +0200
Giulio Benetti <giulio.benetti@benettiengineering.com> wrote:
> Hi Steve,
>
> On 30/09/23 22:28, Steven Rostedt wrote:
> > On Sat, 30 Sep 2023 22:13:39 +0200
> > Giulio Benetti <giulio.benetti@benettiengineering.com> wrote:
> >
> > Hi Giulio,
> >
> > Thanks for the patch, but could you please add a change log to explain
> > why this patch is needed? I'm not saying it isn't but I'd like to know
> > the rational for disabling documentation.
>
> Sure, same for libtracefs then.
>
> Would it be possible to release a minor version after committing?
> This is because I've updated libtraceevent, libtracefs and trace-cmd in
> buildroot but without using meson due to asciidoc not found(in Buildroot
> we never produce documentation for target).
Sure, it's time for me to start working on the user space libraries
again anyway (I toggle my time between the kernel and user space
tracing).
>
> So if you could release new versions of libtraceevent and libtracefs
> after committing V2 patches I could bump in Buildroot and use meson
> that is very clean compared to the actual Makefile custom build calls.
>
> Going to send V2 patches in the meanwhile.
>
> Best regards
Appreciated!
-- Steve
next prev parent reply other threads:[~2023-09-30 20:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-30 20:13 [PATCH] libtraceevent: add option to disable documentation Giulio Benetti
2023-09-30 20:28 ` Steven Rostedt
2023-09-30 20:32 ` Giulio Benetti
2023-09-30 20:39 ` Steven Rostedt [this message]
2023-09-30 20:42 ` Giulio Benetti
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=20230930163900.152d49fd@rorschach.local.home \
--to=rostedt@goodmis.org \
--cc=giulio.benetti@benettiengineering.com \
--cc=linux-trace-devel@vger.kernel.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).