From: Steven Rostedt <rostedt@goodmis.org>
To: Jiri Olsa <jolsa@redhat.com>
Cc: 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>,
Tony Jones <tonyj@suse.de>, 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:19:50 -0400 [thread overview]
Message-ID: <20201012111950.55a73588@gandalf.local.home> (raw)
In-Reply-To: <20201012101208.GF1099489@krava>
On Mon, 12 Oct 2020 12:12:08 +0200
Jiri Olsa <jolsa@redhat.com> wrote:
> On Wed, Oct 07, 2020 at 01:07:50PM -0400, Steven Rostedt wrote:
> > I split out tools/lib/traceevent from the kernel tree using "git subtree",
> > which recreates all the commits of a directory and makes that directory a
> > stand alone. I then updated the Makefiles, and copied over some of the
> > header files used to build the library. I pushed this up to:
> >
> > https://git.kernel.org/pub/scm/libs/libtrace/libtraceevent.git/
> >
> > My hope is that this will now be the source of all updates to the
> > libtraceevent library that can be used as a stand alone package that both
> > perf and tracecmd can use. I would also like powertop and rasdaemon to use
> > this as well.
>
> hi,
> I'm adding this as fedora package, is there a source arhive somewhere
> in git.kernel.org for libtraceevent that spec could download?
>
Hi Jiri!
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. But I
wanted to fix all the packaging bugs before doing so. I hope this doesn't
make it into a catch-22. Where you can't package till there's a source
tarball, but I can't make a source tarball until I know you can package
it ;-)
-- Steve
next prev parent reply other threads:[~2020-10-12 15:19 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 [this message]
2020-10-12 15:32 ` Sudip Mukherjee
2020-10-12 18:41 ` Tony Jones
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=20201012111950.55a73588@gandalf.local.home \
--to=rostedt@goodmis.org \
--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=sudipm.mukherjee@gmail.com \
--cc=sztsian@gmail.com \
--cc=tonyj@suse.de \
--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;
as well as URLs for NNTP newsgroup(s).