From: Steven Rostedt <rostedt@goodmis.org>
To: Zamir SUN <sztsian@gmail.com>
Cc: tz.stoyanov@gmail.com, linux-trace-devel@vger.kernel.org
Subject: Re: [PATCH] Documentation: Fix include level of Makefile scripts
Date: Fri, 9 Oct 2020 10:54:41 -0400 [thread overview]
Message-ID: <20201009105441.3c92e560@gandalf.local.home> (raw)
In-Reply-To: <7897620c-3039-5e4f-09d9-41606673fa63@gmail.com>
On Thu, 8 Oct 2020 15:30:08 +0800
Zamir SUN <sztsian@gmail.com> wrote:
> Note, this patch is for libtraceevent.
>
> And I think it makes more sense to port the missing
> scripts/utilities.mak by the maintainer rather than sending a patchset
> with lots of historical commits from kernel, so I did not include that
> part here.
>
> HTH.
Thanks!
I reverted the copy and brought over the history of the Makefiles, scripts
and include headers. I also included utilities.mak.
When this becomes something that can be installed as a package, I'll give
it an official tag: libtraceevent-v1.1.0
-- Steve
next prev parent reply other threads:[~2020-10-09 14:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-08 7:18 [PATCH] Documentation: Fix include level of Makefile scripts sztsian
2020-10-08 7:30 ` Zamir SUN
2020-10-09 14:54 ` Steven Rostedt [this message]
2020-10-12 12:30 ` Zamir SUN
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=20201009105441.3c92e560@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=sztsian@gmail.com \
--cc=tz.stoyanov@gmail.com \
/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).