From: Tony Jones <tonyj@suse.de>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Jiri Olsa <jolsa@redhat.com>, LKML <linux-kernel@vger.kernel.org>,
Linux Trace Devel <linux-trace-devel@vger.kernel.org>,
Zamir SUN <sztsian@gmail.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
zsun@redhat.com, Vitaly Chikunov <vt@altlinux.org>,
Tzvetomir Stoyanov <tstoyanov@vmware.com>,
Yordan Karadzhov <ykaradzhov@vmware.com>,
Ben Hutchings <ben@decadent.org.uk>,
Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
John Kacur <jkacur@redhat.com>,
Clark Williams <williams@redhat.com>,
powertop@lists.01.org, Al Stone <ahs3@debian.org>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Subject: Re: [ANNOUNCE] libtraceevent.git
Date: Mon, 12 Oct 2020 11:41:20 -0700 [thread overview]
Message-ID: <20201012184120.GN13697@suse.de> (raw)
In-Reply-To: <20201012111950.55a73588@gandalf.local.home>
On Mon, Oct 12, 2020 at 11:19:50AM -0400, Steven Rostedt wrote:
> Once it's shown that it works for all the package maintainers, I will tag
> it which should create the tarballs automatically on the above link.
Hi.
It builds fine for me after manually creating the tarball from git.
Once there is an official versioned tarball I'll push it into
openSUSE.
I presume some perf Makefile changes will be forthcoming to use it,
rather than continuing to force build it out of TRACE_EVENT_DIR
Tony
next prev parent reply other threads:[~2020-10-12 18:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-07 17:07 [ANNOUNCE] libtraceevent.git Steven Rostedt
2020-10-12 10:12 ` Jiri Olsa
2020-10-12 10:19 ` Zamir SUN
2020-10-12 10:35 ` Jiri Olsa
2020-10-12 15:19 ` Steven Rostedt
2020-10-12 15:32 ` Sudip Mukherjee
2020-10-12 18:41 ` Tony Jones [this message]
2020-10-12 18:52 ` Jiri Olsa
2020-10-12 19:13 ` Steven Rostedt
2020-10-12 19:17 ` Steven Rostedt
2020-10-12 20:24 ` Sudip Mukherjee
2020-10-13 3:06 ` Zamir SUN
2020-10-13 13:02 ` Steven Rostedt
2020-10-14 10:08 ` Sudip Mukherjee
2020-10-14 13:44 ` Steven Rostedt
2020-10-14 12:56 ` Zamir SUN
2020-10-14 17:25 ` Steven Rostedt
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=20201012184120.GN13697@suse.de \
--to=tonyj@suse.de \
--cc=acme@kernel.org \
--cc=ahs3@debian.org \
--cc=ben@decadent.org.uk \
--cc=jkacur@redhat.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=powertop@lists.01.org \
--cc=rostedt@goodmis.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=sztsian@gmail.com \
--cc=tstoyanov@vmware.com \
--cc=vt@altlinux.org \
--cc=williams@redhat.com \
--cc=ykaradzhov@vmware.com \
--cc=zsun@redhat.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