From: Steven Rostedt <rostedt@goodmis.org>
To: Linux Trace Devel <linux-trace-devel@vger.kernel.org>
Cc: Tzvetomir Stoyanov <tz.stoyanov@gmail.com>,
Yordan Karadzhov <y.karadz@gmail.com>,
Daniel Bristot de Oliveira <bristot@redhat.com>,
Ian Rogers <irogers@google.com>,
Jerome Marchand <jmarchan@redhat.com>,
John 'Warthog9' Hawley <warthog9@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>,
Sameeruddin shaik <sameeross1994@gmail.com>
Subject: Getting ready for libtracefs 1.3
Date: Wed, 23 Feb 2022 10:42:06 -0500 [thread overview]
Message-ID: <20220223104206.7cb5e8ce@gandalf.local.home> (raw)
I'm in my final testing phase of libtracefs.
If there's anything you want added, or think should change, please let me
know soon. I may try to release it by end of (my) day today.
Thanks everyone that helped with this release!
-- Steve
reply other threads:[~2022-02-23 15:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220223104206.7cb5e8ce@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=bristot@redhat.com \
--cc=irogers@google.com \
--cc=jmarchan@redhat.com \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linux-trace-devel@vger.kernel.org \
--cc=sameeross1994@gmail.com \
--cc=tz.stoyanov@gmail.com \
--cc=warthog9@kernel.org \
--cc=y.karadz@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).