From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mailfilter02.viettel.com.vn (mailfilter02.viettel.com.vn [125.235.240.54]) by dpdk.org (Postfix) with ESMTP id 85FCF5F2E for ; Sun, 25 Mar 2018 16:31:11 +0200 (CEST) X-IronPort-AV: E=Sophos;i="5.48,360,1517850000"; d="scan'208";a="74827876" Received: from 125.235.240.45.adsl.viettel.vn (HELO mta2.viettel.com.vn) ([125.235.240.45]) by mailfilter02.viettel.com.vn with ESMTP; 25 Mar 2018 21:31:09 +0700 Received: from localhost (localhost [127.0.0.1]) by mta2.viettel.com.vn (Postfix) with ESMTP id D2884692DEF; Sun, 25 Mar 2018 21:31:07 +0700 (ICT) Received: from mta2.viettel.com.vn ([127.0.0.1]) by localhost (mta2.viettel.com.vn [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id 40siOJ2y64CZ; Sun, 25 Mar 2018 21:31:07 +0700 (ICT) Received: from localhost (localhost [127.0.0.1]) by mta2.viettel.com.vn (Postfix) with ESMTP id AF7EC692DF1; Sun, 25 Mar 2018 21:31:07 +0700 (ICT) X-Virus-Scanned: amavisd-new at Received: from mta2.viettel.com.vn ([127.0.0.1]) by localhost (mta2.viettel.com.vn [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id B_i12b46vPPz; Sun, 25 Mar 2018 21:31:07 +0700 (ICT) Received: from zimbra.viettel.com.vn (mailbox4.viettel.com.vn [10.30.182.139]) by mta2.viettel.com.vn (Postfix) with ESMTP id 86A0C692DEF; Sun, 25 Mar 2018 21:31:07 +0700 (ICT) To: shreyansh jain Cc: Thomas Monjalon , users@dpdk.org Message-ID: <111563022.683655.1521988267552.JavaMail.zimbra@viettel.com.vn> In-Reply-To: References: <642873809.317162.1521959350049.JavaMail.zimbra@viettel.com.vn> <1123861846.317257.1521959367262.JavaMail.zimbra@viettel.com.vn> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [113.178.69.142] X-Mailer: Zimbra 8.0.9_GA_6191 (ZimbraWebClient - GC64 (Linux)/8.0.9_GA_6191) Thread-Topic: Apply patches from the mailing list Thread-Index: xOy20c6DQPB6bSQaSEmkERYhQv1mAc4arr8gUCX1pXo= MilterAction: FORWARD Date: Sun, 25 Mar 2018 21:31:07 +0700 (ICT) From: longtb5@viettel.com.vn Subject: Re: [dpdk-users] Apply patches from the mailing list X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Mar 2018 14:31:12 -0000 Hi Shreyansh, After my email I figured out your 2a). But yeah having to register/login was a nuisance and not very intuitive especially for people like me who had had no experience working with patchwork or mailing lists before. > Maybe you can go ahead and send across a patch for a method you find best and efficient. > Others can add their way/suggestions and I am confident Thomas would be happy to accept > a documentation improvement patch. Echoing this. A section in the contributor guideline just like the one I followed when I pushed my first patch would be very helpful indeed. Regards, -BL ----- Original Message ----- From: "shreyansh jain" To: longtb5@viettel.com.vn, "Thomas Monjalon" Cc: users@dpdk.org Sent: Sunday, March 25, 2018 6:05:30 PM Subject: RE: Apply patches from the mailing list > -----Original Message----- > From: users [mailto:users-bounces@dpdk.org] On Behalf Of > longtb5@viettel.com.vn > Sent: Sunday, March 25, 2018 11:59 AM > To: users@dpdk.org > Subject: [dpdk-users] Apply patches from the mailing list > > A very basic question, but how do I apply some of the patches that > were put on the dev mailing list to try it out? I already looked at > the next- subtrees but apparently even major patch set such as the new > packet framework/ip_pipeline is not in there (yet). This is what I do: 1. Access http://dpdk.org/dev/patchwork/project/dpdk/list/ and search for patches from the author. This has all the patches posted to Mailing List - with their state (that is, for example, superseded if a series has been superseded with another version) 2. You have three options: a) Either select all patches (you will need to register/login) in a series and add to "bundle" and download that bundle as mbox b) Select individual patch and look for "download patch" or "download mbox" link and manually download them. OR, one I use most frequently: b) Copy the link to patch (for example, http://dpdk.org/dev/patchwork/patch/36473/) and append "mbox" to it (http://dpdk.org/dev/patchwork/patch/36473/mbox) Then, $ wget -O - | git am One can easily make a script which can do the steps (1)>(2b) above based on a given patch ID (last integer in the link to patch). Maybe there is a better and efficient way - this is just what I do. :) > > The contributor guideline only has sections for submitting patches to > the mailing list, not pulling and applying patches for local testing. > I know of dpdk patchwork but there are no instructions provided. Maybe you can go ahead and send across a patch for a method you find best and efficient. Others can add their way/suggestions and I am confident Thomas would be happy to accept a documentation improvement patch. - Shreyansh