From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ig0-f176.google.com (mail-ig0-f176.google.com [209.85.213.176]) by dpdk.org (Postfix) with ESMTP id B88AB66DB for ; Wed, 11 May 2016 23:22:45 +0200 (CEST) Received: by mail-ig0-f176.google.com with SMTP id lr7so42964958igb.1 for ; Wed, 11 May 2016 14:22:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=broadcom.com; s=google; h=mime-version:date:message-id:subject:from:to; bh=W2Shd9IrrJj4y8HovmLfRhc22Xx04IftKUBHYPFVoLg=; b=IixdQVVQZzGIGXFNg1nQe4LuCUt/FDqUmBwyytDyd3I2LMNSJcySu6hgNHpwcAwmj7 L7GEFN0GNP77linIHoCbl/0hm6axgu64tdmL/qzFJ7na+9Iye9slrBYPl5F3y3gLd9+R Yu6B+KZG2Ts0ZDFbX2roZWlM9Hke6hRSbFI0w= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to; bh=W2Shd9IrrJj4y8HovmLfRhc22Xx04IftKUBHYPFVoLg=; b=Ywy9OgYVTVk1DjSRkN4/UvyJD6Uj/6c0dy6r9UrZopjGKN1lw/18Umh7D8H71mhr7t /Ip2K4XcqcHrRStOZZNUohn35WRNchxEW8p5JsGS+ohvYcLG3yHG9cnOyV9FEdx+HAaP TX5qHflC4pP7efRCOIdLoVG7GLhfViVPM0yEwtJ0XCrzhAarMxELvdlbfMTuQTjSeptm +NjKfhRY7/ZbhrPRCbio8i/HAU4LUNWyZTrCO9xwpQWwH3NFYS3BGR4YiGywXfwNhhr6 sXKDhv4XtPDQLCqp3KdbLcCYIlV933ZWCGhGabNzNCka0LvBftyz8E5VSge65ttA+BRl Nw9w== X-Gm-Message-State: AOPr4FUOpjY4uFLNEq4UBB2nKazLARExgpCTTuDxs9AuMJqzgMUYoIqbVTxrtmttWbI06q+u1+TZRFdXautiEzgf MIME-Version: 1.0 X-Received: by 10.50.236.34 with SMTP id ur2mr5608035igc.54.1463001765071; Wed, 11 May 2016 14:22:45 -0700 (PDT) Received: by 10.36.45.142 with HTTP; Wed, 11 May 2016 14:22:45 -0700 (PDT) Date: Wed, 11 May 2016 14:22:45 -0700 Message-ID: From: Stephen Hurd To: dev@dpdk.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: [dpdk-dev] Updates to large patchsets X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 May 2016 21:22:46 -0000 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? -- Stephen Hurd Principal Engineer - Software Development Broadcom Corporation 949-926-8039 stephen.hurd@broadcom.com