From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: Updates to large patchsets Date: Thu, 12 May 2016 09:43:48 +0200 Message-ID: <4079874.Szl0fMNbYL@xps13> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org To: Stephen Hurd Return-path: Received: from mail-wm0-f48.google.com (mail-wm0-f48.google.com [74.125.82.48]) by dpdk.org (Postfix) with ESMTP id 3D0696968 for ; Thu, 12 May 2016 09:43:50 +0200 (CEST) Received: by mail-wm0-f48.google.com with SMTP id g17so120433643wme.1 for ; Thu, 12 May 2016 00:43:50 -0700 (PDT) In-Reply-To: List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 2016-05-11 14:22, Stephen Hurd: > When submitting an update to a single patch in a large patchset, what's the > preferred method? Do I send a single "[PATCH v2 01/40]" email with the > modified patch or do I send the entire series of 40 patches again? Good question :) It's generally easier to understand if the whole series is sent. If the series is large, it is better to wait to have several changes. If you are almost sure there will be no more change except 1 or 2 small ones, then you can send only these single patches. Anyway, please keep patchwork status updated, i.e. mark old patches as superseded.