From: Jiri Olsa <jolsa@redhat.com>
To: Alexei Starovoitov <ast@fb.com>
Cc: Julia Kartseva <hex@fb.com>,
Andrii Nakryiko <andrii.nakryiko@gmail.com>,
"labbott@redhat.com" <labbott@redhat.com>,
"acme@kernel.org" <acme@kernel.org>,
"debian-kernel@lists.debian.org" <debian-kernel@lists.debian.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Andrey Ignatov <rdna@fb.com>, Yonghong Song <yhs@fb.com>,
"jolsa@kernel.org" <jolsa@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>
Subject: Re: libbpf distro packaging
Date: Mon, 26 Aug 2019 08:42:35 +0200 [thread overview]
Message-ID: <20190826064235.GA17554@krava> (raw)
In-Reply-To: <a00bab9b-dae8-23d8-8de0-3751a1d1b023@fb.com>
On Fri, Aug 23, 2019 at 04:00:01PM +0000, Alexei Starovoitov wrote:
> On 8/23/19 2:22 AM, Jiri Olsa wrote:
> > btw, the libbpf GH repo tag v0.0.4 has 0.0.3 version set in Makefile:
> >
> > VERSION = 0
> > PATCHLEVEL = 0
> > EXTRAVERSION = 3
> >
> > current code takes version from libbpf.map so it's fine,
> > but would be great to start from 0.0.5 so we don't need to
> > bother with rpm patches.. is 0.0.5 planned soon?
>
> Technically we can bump it at any time.
> The goal was to bump it only when new kernel is released
> to capture a collection of new APIs in a given 0.0.X release.
> So that libbpf versions are synchronized with kernel versions
> in some what loose way.
> In this case we can make an exception and bump it now.
I see, I dont think it's worth of the exception now,
the patch is simple or we'll start with 0.0.3
jirka
next prev parent reply other threads:[~2019-08-26 6:42 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-12 19:04 libbpf distro packaging Julia Kartseva
2019-08-13 12:24 ` Jiri Olsa
2019-08-13 14:11 ` Daniel Borkmann
2019-08-13 18:26 ` Andrii Nakryiko
2019-08-13 18:23 ` Andrii Nakryiko
[not found] ` <FA139BA4-59E5-43C7-8E72-C7B2FC1C449E@fb.com>
2019-08-20 22:27 ` Julia Kartseva
2019-08-21 21:09 ` Jiri Olsa
2019-08-23 9:22 ` Jiri Olsa
2019-08-23 16:00 ` Alexei Starovoitov
2019-08-26 6:42 ` Jiri Olsa [this message]
2019-08-27 22:30 ` Julia Kartseva
2019-08-28 7:12 ` Jiri Olsa
2019-09-30 11:13 ` Jiri Olsa
2019-09-30 18:18 ` Julia Kartseva
2019-10-03 0:50 ` Julia Kartseva
2019-10-03 11:10 ` Jiri Olsa
2019-10-03 16:24 ` Andrii Nakryiko
2019-10-03 17:29 ` Jiri Olsa
2019-10-07 0:25 ` Julia Kartseva
2019-10-08 7:39 ` Jiri Olsa
2019-10-11 21:14 ` Julia Kartseva
2019-10-16 10:01 ` Jiri Olsa
2019-12-19 21:37 ` Julia Kartseva
2019-12-20 13:58 ` Jiri Olsa
2020-03-05 0:22 ` Julia Kartseva
2020-03-05 14:18 ` Jiri Olsa
2020-03-10 14:57 ` Jiri Olsa
2020-03-10 17:18 ` Julia Kartseva
2020-03-10 17:49 ` Jiri Olsa
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=20190826064235.GA17554@krava \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=andrii.nakryiko@gmail.com \
--cc=ast@fb.com \
--cc=daniel@iogearbox.net \
--cc=debian-kernel@lists.debian.org \
--cc=hex@fb.com \
--cc=jolsa@kernel.org \
--cc=labbott@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=rdna@fb.com \
--cc=yhs@fb.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.