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 532D228F3 for ; Thu, 22 Feb 2018 11:20:22 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id AE44E20FA8; Thu, 22 Feb 2018 05:20:21 -0500 (EST) Received: from frontend1 ([10.202.2.160]) by compute1.internal (MEProxy); Thu, 22 Feb 2018 05:20:21 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=44Jf6xSOJhe7nLtQivXQWUujJn /zWU8YVg32FkusKNE=; b=UB+S4Gmthg3rNpeXUtPyom2NfOLxg1SSEl50NAPo3r O/BESnYp+j2hzfoRPS2eBjdLD3bPVrA7SFpor+75FdDvYf4NQqpfUwPBYz7X4Vj5 /VTYFFPpYMfADOe10R7ehFC4tzq9N+899QiOiwOvpwoE2k38iAiS247by4oPT3NV g= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=44Jf6x SOJhe7nLtQivXQWUujJn/zWU8YVg32FkusKNE=; b=QTeLMhhjVZqptUUXaJRZo4 8DYmGwNfgvNThkjUWQX6hE4m0p9kvdDudW4j3de3Wzr0u9GZBTT2StmIiqpIjaA6 nkiWhqJXGruWUSZiWztsh7TJlQ9xVooKrwMu6ldtGr9jbZZrMD+eDBwTF59wL+Hd TkvdTX9ybU/j0+10NxsFIZwwN4o2747B5bN78Rkl4e4M6V1CqNvKd/3KzhAnlT31 dgNTiNR35U69t6Szf53ws5QXdBuivspwmap33wTF7K12hloo8UiK8Lb+9xNHz3aM PvvQJZTqsNh6q3Orvychhkxvhnc7XpeptDXTdusf9P7kxrkVTNq1+Ws8vG7ANfoA == X-ME-Sender: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 450C47E070; Thu, 22 Feb 2018 05:20:21 -0500 (EST) From: Thomas Monjalon To: Ferruh Yigit , Yasufumi Ogawa Cc: Nakamura Hioryuki , spp@dpdk.org Date: Thu, 22 Feb 2018 11:19:56 +0100 Message-ID: <1545048.PFpTTTFbJg@xps> In-Reply-To: <180a0ff3-a4cf-d54b-403f-2ee287f30409@intel.com> References: <201802080556.w185uBLt011286@imss03.silk.ntt-tx.co.jp> <180a0ff3-a4cf-d54b-403f-2ee287f30409@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" 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:20:22 -0000 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?