[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200106182229.3sntyytugif4hesi@chatter.i7.local>
Date: Mon, 6 Jan 2020 13:22:29 -0500
From: Konstantin Ryabitsev <konstantin@...uxfoundation.org>
To: Jiri Olsa <jolsa@...hat.com>
Cc: Steven Rostedt <rostedt@...dmis.org>,
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>,
users@...ux.kernel.org
Subject: Re: [RFC] tools lib traceevent: How to do library versioning being
in the Linux kernel source?
On Mon, Jan 06, 2020 at 04:19:02PM +0100, Jiri Olsa wrote:
> > I wonder if there should be a:
> >
> > git://git.kernel.org/pub/scm/utils/lib/
> >
> > directory to have:
> >
> > git://git.kernel.org/pub/scm/utils/lib/traceevent/
> > git://git.kernel.org/pub/scm/utils/lib/libbpf/
> > git://git.kernel.org/pub/scm/utils/lib/libperf/
We already have 'pub/scm/libs' so I suggest we just place things there:
pub/scm/libs/traceevent
pub/scm/libs/libbpf
pub/scm/libs/libperf
Normally, we do a whole subdir, but that can be unnecessary, especially
to avoid repetitions like:
pub/scm/libs/libgpiod/libgpiod.git
If the suggested locations work for you, just email helpdesk@...nel.org
requesting their creation, and please specify who should have push
access to them.
-K
Powered by blists - more mailing lists