WireGuard Archive on lore.kernel.org
 help / color / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: organization of wireguard linux kernel repos moving forward
Date: Thu, 26 Dec 2019 18:45:05 +0100
Message-ID: <CAHmME9rArDcBAhdj2roaoVeC+S_v=+KdEvrvY3gPMnApnLdmJA@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9p1-5hQXv5QNqqHT+OBjn-vf16uAU2HtYcmwKMtLhnsTA@mail.gmail.com>

On Mon, Dec 9, 2019 at 12:56 PM Jason A. Donenfeld <Jason@zx2c4.com> wrote:
> With WireGuard in net-next, it's time to break up the monolithic repo
> we've been using for development into something a bit more manageable
> and in line with ordinary kernel development.
> Right now the "WireGuard.git" repo has been structured as an out of
> tree module, alongside a subdirectory for tools, one for scripts, one
> for tests, and another for a super gnarly compat layer that makes the
> thing work on all kernels going back to 3.10. We're going to break
> this up into three repositories:
> 1) wireguard-linux.git will be a full Linux tree, with wireguard
> changes, and regularly merge in net/net-next, and have things from
> there posted on netdev like usual for review. This repo won't be an
> out of tree module any more, obviously.
> https://git.zx2c4.com/wireguard-linux/
> 2) wireguard-tools.git will have the userspace utilities and scripts,
> such as wg(8) and wg-quick(8), and be easily packageable by distros.
> https://git.zx2c4.com/wireguard-tools/
> 3) wireguard-linux-compat.git will be an out-of-tree module containing
> the aforementioned horrific compat.h layer. New development will go
> into upstream wireguard-linux.git, but we'll do our best to keep
> things mostly working for as long as it makes sense and is feasible.
> https://git.zx2c4.com/wireguard-linux-compat/
> The CI that runs on build.wireguard.com will also see some updates to
> reflect these adjustments, and also more closely align with the
> net-next tree. Additionally, I'm interested to see if I can make our
> CI useful for a variety of things in net/ and drivers/net/ instead of
> just for wireguard.

The above changes are now complete.
WireGuard mailing list

      parent reply index

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-09 11:56 Jason A. Donenfeld
2019-12-09 12:43 ` Toke Høiland-Jørgensen
2019-12-09 12:49   ` Jason A. Donenfeld
2019-12-09 16:01     ` Toke Høiland-Jørgensen
2019-12-09 16:18     ` David Ahern
2019-12-09 16:36       ` Toke Høiland-Jørgensen
2019-12-26 17:45 ` Jason A. Donenfeld [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAHmME9rArDcBAhdj2roaoVeC+S_v=+KdEvrvY3gPMnApnLdmJA@mail.gmail.com' \
    --to=jason@zx2c4.com \
    --cc=wireguard@lists.zx2c4.com \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

WireGuard Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/wireguard/0 wireguard/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 wireguard wireguard/ https://lore.kernel.org/wireguard \
	public-inbox-index wireguard

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git