From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id 81C3B5677 for ; Mon, 15 Feb 2016 15:30:49 +0100 (CET) Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by orsmga101.jf.intel.com with ESMTP; 15 Feb 2016 06:30:48 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.22,450,1449561600"; d="scan'208";a="915340172" Received: from bricha3-mobl3.ger.corp.intel.com ([10.237.208.63]) by fmsmga002.fm.intel.com with SMTP; 15 Feb 2016 06:30:44 -0800 Received: by (sSMTP sendmail emulation); Mon, 15 Feb 2016 14:30:44 +0025 Date: Mon, 15 Feb 2016 14:30:44 +0000 From: Bruce Richardson To: dev@dpdk.org Message-ID: <20160215143043.GA17920@bricha3-MOBL3> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Organization: Intel Shannon Ltd. User-Agent: Mutt/1.5.23 (2014-03-12) Subject: [dpdk-dev] rebasing of dpdk-next-net tree X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Feb 2016 14:30:49 -0000 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