From: Steven Rostedt <rostedt@goodmis.org>
To: LKML <linux-kernel@vger.kernel.org>,
Linux Trace Devel <linux-trace-devel@vger.kernel.org>,
"linux-trace-users@vger.kernel.org"
<linux-trace-users@vger.kernel.org>,
Daniel Bristot de Oliveira <bristot@redhat.com>
Cc: Zamir SUN <sztsian@gmail.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Jiri Olsa <jolsa@redhat.com>,
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>,
Jes Sorensen <jes.sorensen@gmail.com>
Subject: Re: [ANNOUNCE] libtracefs 1.3
Date: Wed, 23 Feb 2022 19:09:52 -0500 [thread overview]
Message-ID: <20220223190952.084f4685@rorschach.local.home> (raw)
In-Reply-To: <20220223183939.3650aabd@rorschach.local.home>
[ Resend as one of my emails was corrupted]
On Wed, 23 Feb 2022 18:39:39 -0500
Steven Rostedt <rostedt@goodmis.org> wrote:
> Long over due, but libtracefs 1.3 has finally been released!
And I forgot to post the links:
git repo: https://git.kernel.org/pub/scm/libs/libtrace/libtracefs.git/
tarball: https://git.kernel.org/pub/scm/libs/libtrace/libtracefs.git/snapshot/libtracefs-1.3.0.tar.gz
man pages: https://www.trace-cmd.org/Documentation/libtracefs/libtracefs.html
-- Steve
prev parent reply other threads:[~2022-02-24 0:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 23:39 [ANNOUNCE] libtracefs 1.3 Steven Rostedt
2022-02-24 0:09 ` Steven Rostedt [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=20220223190952.084f4685@rorschach.local.home \
--to=rostedt@goodmis.org \
--cc=acme@kernel.org \
--cc=ben@decadent.org.uk \
--cc=bristot@redhat.com \
--cc=jes.sorensen@gmail.com \
--cc=jkacur@redhat.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=linux-trace-users@vger.kernel.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).