netdev - Re: iproute2 net-next

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Mon, 22 Jan 2018 09:07:24 -0700
From:   David Ahern <dsa@...ulusnetworks.com>
To:     Jakub Kicinski <kubakici@...pl>
Cc:     Marcelo Ricardo Leitner <marcelo.leitner@...il.com>,
        Stephen Hemminger <stephen@...workplumber.org>,
        Jiri Pirko <jiri@...nulli.us>,
        Daniel Borkmann <daniel@...earbox.net>,
        Leon Romanovsky <leon@...nel.org>, netdev@...r.kernel.org
Subject: Re: iproute2 net-next

On 1/15/18 8:29 PM, Jakub Kicinski wrote:
> About the branches - what should we base our patches on for net-next?
> Most -next repos just use the master, but it seems that in case of
> iproute2-next.git the net-next branch is still active, and there is
> an inactive net-next branch in iproute2.git..  Is this transitional or
> will it stay this way?

The master branch for iproute2-next tree has been updated to be the
branch for -next patches and the net-next branch has been deleted.