From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 69D2BA00E6 for ; Fri, 9 Aug 2019 04:19:32 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id CC2682B95; Fri, 9 Aug 2019 04:19:30 +0200 (CEST) Received: from dish-sg.nttdocomo.co.jp (dish-sg.nttdocomo.co.jp [202.19.227.74]) by dpdk.org (Postfix) with ESMTP id 598C92B8C for ; Fri, 9 Aug 2019 04:19:28 +0200 (CEST) X-dD-Source: Outbound Received: from zssg-mailmd102.ddreams.local (zssg-mailmd900.ddreams.local [10.160.172.63]) by zssg-mailou102.ddreams.local (Postfix) with ESMTP id D7FC4120126 for ; Fri, 9 Aug 2019 11:19:24 +0900 (JST) Received: from t131sg-mailcc12.ddreams.local (t131sg-mailcc12.ddreams.local [100.66.31.87]) by zssg-mailmd102.ddreams.local (dDREAMS) with ESMTP id <0PVY004HP6GCGV90@dDREAMS> for dev@dpdk.org; Fri, 09 Aug 2019 11:19:24 +0900 (JST) Received: from t131sg-mailcc11 (localhost [127.0.0.1]) by t131sg-mailcc12.ddreams.local (unknown) with SMTP id x792JOeA031210 for ; Fri, 9 Aug 2019 11:19:24 +0900 Received: from zssg-mailmf105.ddreams.local (unknown [127.0.0.1]) by zssg-mailmf105.ddreams.local (Postfix) with ESMTP id 4CC977E6036 for ; Fri, 9 Aug 2019 11:19:13 +0900 (JST) Received: from zssg-mailmf105.ddreams.local (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 4B3BE8E605D for ; Fri, 9 Aug 2019 11:19:13 +0900 (JST) Received: from localhost (unknown [127.0.0.1]) by IMSVA (Postfix) with SMTP id 48E058E6058 for ; Fri, 9 Aug 2019 11:19:13 +0900 (JST) X-IMSS-HAND-OFF-DIRECTIVE: localhost:10026 Received: from zssg-mailmf105.ddreams.local (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id B27C98E6060 for ; Fri, 9 Aug 2019 11:19:12 +0900 (JST) Received: from zssg-mailua106.ddreams.local (unknown [10.160.172.62]) by zssg-mailmf105.ddreams.local (Postfix) with ESMTP for ; Fri, 9 Aug 2019 11:19:12 +0900 (JST) Received: from [10.87.198.18] (unknown [10.160.183.129]) by zssg-mailua106.ddreams.local (dDREAMS) with ESMTPA id <0PVY00T196FYUD50@dDREAMS> for dev@dpdk.org; Fri, 09 Aug 2019 11:19:10 +0900 (JST) Date: Fri, 09 Aug 2019 11:19:10 +0900 From: Hideyuki Yamashita In-reply-to: <26FA93C7ED1EAA44AB77D62FBE1D27BAB790C9E0@IRSMSX108.ger.corp.intel.com> References: <26FA93C7ED1EAA44AB77D62FBE1D27BAB790C9E0@IRSMSX108.ger.corp.intel.com> Message-id: <20190809111910.D110.17218CA3@ntt-tx.co.jp_1> MIME-version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit X-Mailer: Becky! ver. 2.74.02 [ja] X-TM-AS-GCONF: 00 To: "dev@dpdk.org" Subject: [dpdk-dev] which is the code base when submitting patch around end of September 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: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Hello Experts, Very basic question to create patch. I am planning to post patch set which introduce new functionality (not bug fix ). Note that I will post the patch set on end of September. Q1. If I post patch set to dev-ml, which is the code base? Source code which is retrieved from "git clone" ? Or tar ball of previous version like "dpdk-19.05.tar.gz"? Q2. If review of the patch starts around October, when will the patch will be merged, if patch is good one. 19.11 LTS? or 20.02? (Are there any rule or deadlines?) Thanks in advance, Hideyuki Yamashita NTT TechnoCross