From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by dpdk.org (Postfix) with ESMTP id 9803F2BE5 for ; Thu, 22 Feb 2018 11:26:58 +0100 (CET) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga003.jf.intel.com ([10.7.209.27]) by fmsmga104.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 22 Feb 2018 02:26:57 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.47,377,1515484800"; d="scan'208";a="29817609" Received: from fyigit-mobl1.ger.corp.intel.com (HELO [10.237.220.35]) ([10.237.220.35]) by orsmga003.jf.intel.com with ESMTP; 22 Feb 2018 02:26:55 -0800 To: Thomas Monjalon , Yasufumi Ogawa Cc: Nakamura Hioryuki , spp@dpdk.org References: <201802080556.w185uBLt011286@imss03.silk.ntt-tx.co.jp> <180a0ff3-a4cf-d54b-403f-2ee287f30409@intel.com> <1545048.PFpTTTFbJg@xps> From: Ferruh Yigit Message-ID: Date: Thu, 22 Feb 2018 10:26:55 +0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <1545048.PFpTTTFbJg@xps> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [spp] [spp 02181] Re: [PATCH 4/9] spp_vf: add BSD license X-BeenThere: spp@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Soft Patch Panel List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Feb 2018 10:26:59 -0000 On 2/22/2018 10:19 AM, Thomas Monjalon wrote: > 22/02/2018 11:13, Ferruh Yigit: >> On 2/22/2018 8:10 AM, Yasufumi Ogawa wrote: >>> I did not think of patchwork. I think it is good idea if SPP can use >>> patchwork for patch management. >>> >>> Although I am not sure if it is possible to use patchwork on dpdk.org, >>> do you have any idea for using it for SPP, or allowed only for 'dev'? >> >> I know from other projects, it is technically possible to share single patchwork >> for multiple mail list. But not sure how difficult to setup or maintain that model. >> >> cc'ed Thomas for comment. > > Yes we could do it. > But honestly, it is not the right timing. > We should migrate to a new server with a new patchwork version first. > I can add this requirement in the migration task. > It may take few months before it is done. Is it OK? I believe it is not urgent, doing this while migrating to new server makes sense to me.