From mboxrd@z Thu Jan  1 00:00:00 1970
From: Bruce Richardson <bruce.richardson@intel.com>
Subject: rebasing of dpdk-next-net tree
Date: Mon, 15 Feb 2016 14:30:44 +0000
Message-ID: <20160215143043.GA17920@bricha3-MOBL3>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
To: dev@dpdk.org
Return-path: <dev-bounces@dpdk.org>
Received: from mga02.intel.com (mga02.intel.com [134.134.136.20])
 by dpdk.org (Postfix) with ESMTP id 81C3B5677
 for <dev@dpdk.org>; Mon, 15 Feb 2016 15:30:49 +0100 (CET)
Content-Disposition: inline
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

Hi all

just a brief note about the dpdk-next-net tree. As many of you will have noticed
I have starting committing patches to the networking drivers into the
dpdk-next-net tree. For the current release cycle, these will be put onto the
branch rel_16_04.

Please note, though, that this branch will be rebased occasionally, as I
see the need to pull in content from dpdk.org mainline. I will attempt to keep
rebases to a minimum, but they will occur as needed from time to time.

If this causes issues for anyone, please let me know, so that we can come up
with a policy for the dpdk-next-* trees (of which next-net is only the first)
which works for both contributors and maintainers/committers.

Thanks,
/Bruce