[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200102185853.0ed433e4@gandalf.local.home>
Date: Thu, 2 Jan 2020 18:58:53 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Jiri Olsa <jolsa@...hat.com>
Cc: Sudip Mukherjee <sudipm.mukherjee@...il.com>,
Ingo Molnar <mingo@...nel.org>,
Arnaldo Carvalho de Melo <acme@...nel.org>,
Namhyung Kim <namhyung@...nel.org>,
Masami Hiramatsu <mhiramat@...nel.org>,
Linux Trace Devel <linux-trace-devel@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [RFC] tools lib traceevent: How to do library versioning being
in the Linux kernel source?
On Fri, 3 Jan 2020 00:49:50 +0100
Jiri Olsa <jolsa@...hat.com> wrote:
> > Should we move libtraceevent into a stand alone git repo (on
> > kernel.org), that can have tags and branches specifically for it? We
> > can keep a copy in the Linux source tree for perf to use till it
>
> so libbpf 'moved' for this reason to github repo,
> but keeping the kernel as the true/first source,
> and updating github repo when release is ready
>
> libbpf github repo is then source for fedora (and others)
> package
Ah, so perhaps I should follow this? I could keep it a kernel.org repo
(as I rather have it there anyway).
We can have the tools/lib/traceevent be the main source, but then just
copy it to the stand alone for releases.
Sudip, would this work for you too? (and yes, I plan on acking that
patch for the -ldl change, after looking at it a little bit more).
-- Steve
Powered by blists - more mailing lists