From: Steven Rostedt <rostedt@goodmis.org>
To: Zamir SUN <sztsian@gmail.com>
Cc: Tony Jones <tonyj@suse.de>, Jiri Olsa <jolsa@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
Linux Trace Devel <linux-trace-devel@vger.kernel.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
"Ziqian SUN (Zamir)" <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>, Al Stone <ahs3@debian.org>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Subject: Re: [ANNOUNCE] libtraceevent.git
Date: Wed, 14 Oct 2020 13:25:26 -0400 [thread overview]
Message-ID: <20201014132526.70b8684c@gandalf.local.home> (raw)
In-Reply-To: <7997c7e5-481e-a1d6-d785-f1ed18ebf3d4@gmail.com>
On Wed, 14 Oct 2020 20:56:53 +0800
Zamir SUN <sztsian@gmail.com> wrote:
> >
> > So should I just add that one patch and tag it?
> >
>
> That would be great, at least for Fedora packaging.
I'm going with version 1.1.0 and not following the kernel versioning, as
that would just add to the confusion.
Here's the tarball:
https://git.kernel.org/pub/scm/libs/libtrace/libtraceevent.git/snapshot/libtraceevent-1.1.0.tar.gz
-- Steve
prev parent reply other threads:[~2020-10-14 17:25 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
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 [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=20201014132526.70b8684c@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=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).