[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <09dc06e1-8b24-03cd-626b-f77fabf232d2@cumulusnetworks.com>
Date: Tue, 16 Jan 2018 11:06:19 -0800
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 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.
Powered by blists - more mailing lists