All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Thaler <dthaler@microsoft.com>
To: Quentin Monnet <quentin@isovalent.com>, bpf <bpf@vger.kernel.org>,
	Networking <netdev@vger.kernel.org>
Cc: Jakub Kicinski <kuba@kernel.org>, Andrii Nakryiko <andrii@kernel.org>
Subject: RE: Bpftool mirror now available
Date: Thu, 20 Jan 2022 14:19:05 +0000	[thread overview]
Message-ID: <CH2PR21MB14640448106792E7197A042CA35A9@CH2PR21MB1464.namprd21.prod.outlook.com> (raw)
In-Reply-To: <267a35a6-a045-c025-c2d9-78afbf6fc325@isovalent.com>

Quentin Monnet <quentin@isovalent.com> wrote:
> Hi, I have the pleasure to announce the availability of a mirror for bpftool on GitHub, at the following URL:
> [...]
> 3. Another objective was to help other projects build on top of the existing sources for bpftool. I'm thinking in
> particular of eBPF-for-Windows, which has been working on a proof-of-concept port of the tool for Windows [1]. 
> Bpftool's mirror keeps the minimal amount of necessary headers, and stripped most of them from the definitions
> that are not required in our context, which should make it easier to uncouple bpftool from Linux.
> [...]
> Just to make it clear, bpftool's mirror does not change the fact that all bpftool development happens on the
> kernel mailing-lists (in particular, the BPF mailing-list), and that the sources hosted in the kernel repository
> remain the reference for the tool. At this time the GitHub repository is just a mirror, and will not accept pull
> requests on bpftool's sources.

Thanks Quentin, this is a great first step!   I can update the ebpf-for-windows project to use this as a submodule.

Longer term, is the goal to make the mirror be the authoritative reference, or to make the Linux kernel repository
not be Linux-only but accept non-Linux patches to bpftool?

Dave

  parent reply	other threads:[~2022-01-20 14:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-19 14:47 Bpftool mirror now available Quentin Monnet
2022-01-20  6:25 ` Andrii Nakryiko
2022-01-20 12:35   ` Quentin Monnet
2022-01-20 19:07     ` Andrii Nakryiko
2022-01-24 10:37       ` Quentin Monnet
2022-01-20 14:19 ` Dave Thaler [this message]
2022-01-24 12:13   ` Quentin Monnet
2022-01-25  3:39     ` Dave Thaler
2022-01-25 21:42       ` Daniel Borkmann

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=CH2PR21MB14640448106792E7197A042CA35A9@CH2PR21MB1464.namprd21.prod.outlook.com \
    --to=dthaler@microsoft.com \
    --cc=andrii@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=quentin@isovalent.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.