From mboxrd@z Thu Jan  1 00:00:00 1970
From: David Ahern <dsa@cumulusnetworks.com>
Subject: Re: iproute2 net-next
Date: Tue, 16 Jan 2018 11:06:19 -0800
Message-ID: <09dc06e1-8b24-03cd-626b-f77fabf232d2@cumulusnetworks.com>
References: <20171225104919.2568e975@xeon-e3>
 <20171226044743.GK2942@mtr-leonro.local> <20171225221426.57d4af0b@xeon-e3>
 <20171226093547.GC10734@mtr-leonro.local>
 <5f75c535-e4a0-1cfa-d4b0-c3c60d50a1c6@iogearbox.net>
 <20171229085823.GA2000@nanopsycho> <20171229200028.78c1371a@xeon-e3>
 <20180116015614.GA7579@localhost.localdomain>
 <212fd0ef-f2d4-6141-cc6a-d2c36dea95ca@cumulusnetworks.com>
 <20180115192921.1a4c8a24@cakuba.netronome.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Cc: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>,
        Stephen Hemminger <stephen@networkplumber.org>,
        Jiri Pirko <jiri@resnulli.us>,
        Daniel Borkmann <daniel@iogearbox.net>,
        Leon Romanovsky <leon@kernel.org>, netdev@vger.kernel.org
To: Jakub Kicinski <kubakici@wp.pl>
Return-path: <netdev-owner@vger.kernel.org>
Received: from mail-pl0-f50.google.com ([209.85.160.50]:39958 "EHLO
        mail-pl0-f50.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1751060AbeAPTF5 (ORCPT
        <rfc822;netdev@vger.kernel.org>); Tue, 16 Jan 2018 14:05:57 -0500
Received: by mail-pl0-f50.google.com with SMTP id g18so1268744plo.7
        for <netdev@vger.kernel.org>; Tue, 16 Jan 2018 11:05:57 -0800 (PST)
In-Reply-To: <20180115192921.1a4c8a24@cakuba.netronome.com>
Content-Language: en-US
Sender: netdev-owner@vger.kernel.org
List-ID: <netdev.vger.kernel.org>

On 1/15/18 7:29 PM, Jakub Kicinski wrote:
>> Done a few days ago. The new canonical URLs for those repos are:
>>     pub/scm/network/iproute2/iproute2
>>     pub/scm/network/iproute2/iproute2-next
>>
>> So clone URLs
>>     git://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git
>>     https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git
>> and
>>     git://git.kernel.org/pub/scm/network/iproute2/iproute2.git
>>     https://git.kernel.org/pub/scm/network/iproute2/iproute2.git
> 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?

good point. I'll make the current net-next branch in iproute2-next to
master.