From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id CB57B1B53 for ; Tue, 12 Sep 2017 00:03:31 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 61BA920C0F; Mon, 11 Sep 2017 18:03:31 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Mon, 11 Sep 2017 18:03:31 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:message-id :mime-version:subject:to:x-me-sender:x-me-sender:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=vTHXL0r1nQnaySyjN5yGG1Q1yZFjckIS5encVS VG8Zc=; b=qJjhQ0i5GLSGDRM+F3HdChDDYNbpR4MhDU4T23I2WXbUl/45B8X8AD +femwaObZqAXcSTwqAb9pG+p39WcVpJPod6ClBi4vq7UBvPQYljJkRhpXLfgi3ck qC/KEuoVE7hdCMR9U0MWsrU8uh1rq5/O3J0R4W2d79kO1aMtkXUwk= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=fm1; bh=vTHXL0r1nQnaySyjN5 yGG1Q1yZFjckIS5encVSVG8Zc=; b=B8VmU5qXF8oL75OloEbyrNIJdXG3TF5cOr Xi/xwT9YA2gRvlTbGc7JWbomzQHnN5sFzYPiN4Z+t/g8IvfeSuXPDwONZLEZW5Zk pt9T4mQ+/AJfomRLjUeYvWqqIcJVcqCWIROHtLUZ3f2qRT1S8yTpcmVqeJN8VbAp UE+R1AM8cCp8sjae3byP+rAY+zn3N6aca7H3GdU+y05Yuspfr3hnV6BS93NzUvFM BihsQDAC0Wp+F4nB4p+4wAhS27dUb9vhTXn802LU4fo9PejQ5j3HU77lz4alQuE4 GNsIBB+ioF+OipgkpLaEO90Jph9uyFFc4LveRMe1qSt77Ay8+ffw== X-ME-Sender: X-Sasl-enc: U3O318KxoOCfippAHE3t4G7586xp4BUeO0N3avqlIvmM 1505167411 Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 17D7C24009; Mon, 11 Sep 2017 18:03:31 -0400 (EDT) From: Thomas Monjalon To: ferruh.yigit@intel.com, stephen@networkplumber.org Cc: dev@dpdk.org Date: Tue, 12 Sep 2017 00:03:30 +0200 Message-ID: <2737351.pD9poAUtZC@xps> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: [dpdk-dev] git trees organization X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Sep 2017 22:03:32 -0000 Hi all, As you know I am currently the only maintainer of the master tree. It is very convenient because I need to synchronize with others only when pulling "next-*" trees. But the drawback is that I should be available very often to avoid stalled patches waiting in patchwork backlog. I feel it is the good time to move to a slightly different organization. I am working closely with Ferruh Yigit for almost one year, as next-net maintainer, and I think it would be very efficient to delegate him some work for the master tree. I mean that I would use the patchwork delegation to explicitly divide the workload given our different experiences. Ferruh, do you agree taking this new responsibility? At the same time, we can think how to add more git sub-trees: Should we create next-net-intel for Intel networking drivers? Any volunteer? Should we create next-bus for bus API and drivers? Stephen Hemminger is working on a new bus. Would you be interested by taking the responsibility of this git tree? Should we create next-mem for malloc/mempool? Should we take ethdev patches into next-net? Other suggestions?