From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id DCDE96DE096A for ; Tue, 8 Nov 2016 01:15:51 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: 0.084 X-Spam-Level: X-Spam-Status: No, score=0.084 tagged_above=-999 required=5 tests=[AWL=0.104, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=disabled Received: from arlo.cworth.org ([127.0.0.1]) by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iwaIhMpFDLlt for ; Tue, 8 Nov 2016 01:15:50 -0800 (PST) Received: from mail-qt0-f169.google.com (mail-qt0-f169.google.com [209.85.216.169]) by arlo.cworth.org (Postfix) with ESMTPS id 8F1426DE01D0 for ; Tue, 8 Nov 2016 01:15:50 -0800 (PST) Received: by mail-qt0-f169.google.com with SMTP id n6so103637025qtd.1 for ; Tue, 08 Nov 2016 01:15:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nikula-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=xQCXWl4dlhsFua6D89ATFPWhRt3+jus07Bf3s6+qgyM=; b=Du9BZXZ7tRb4IkoTsTcMcqs6rB4kaK/reMGkTedQW+3b/zM6bpBzFc2OIUD/zIclp0 +mDA0CBd2P0QcQRvwfRhKAsPyIk5YUoVTgerIrf76T7NpPGEyVw6cOrhlVQX8hm0bv58 rxnndLjMP6UcgmcG9NJqwthG8O51sLlpCq5vmvrPJJVBwNBrjxhMUrjqcogOKgFiC6yh rrtA49rvaRtO//Z3UHayuuACWheJgwuZW3q/XTw1ffQAWHRl3OfokPWjkuuPuNN57O27 FdgDmWJUgkiVcVo+sxbzEyD/7Ntn9un8qwqaGWh3jf3edDuQxebpiX7RKfkm+jT9BEoG UVVw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=xQCXWl4dlhsFua6D89ATFPWhRt3+jus07Bf3s6+qgyM=; b=ia8B31rdH8VY/5VMSMlyk2/VdWK+yB/JeJ43ZjrWEDDwXpuwwyWJBEa6hwOt3v0ru/ BiIr6X3rEjo2wuW173zuxLEItUwoJ24BekAk9D+jneZN8aMeSY2VF0qFnPy/2MKvjODY 11kipMVEFs4tBItpavYN0h38tSkjwJYhAvW6b55x7F0yt28cCMx6hkRUWEdlUSwvuqJM RGe4Uz0xkMP5OVP0Iv1vKi+Rxk7Mz54M8sW+JNIndhiKk0g/JhX08aNm16+fQUALZWXp CkB8CRrKimREGSaix0TPCX4p3L0s+ZmSpQexgX5oAv6OiM98B1wFTsuWmCsNQ6CRqZfU ypHA== X-Gm-Message-State: ABUngveKq6Yo8GGoQqIPYf97hD4Iz1IdX/3XSTfTLYdBayQa1RcoyyJl5SwQR9LC9SNF4b3jdNVdDiiC8RVIXQ== X-Received: by 10.237.36.170 with SMTP id t39mr11994416qtc.115.1478596548392; Tue, 08 Nov 2016 01:15:48 -0800 (PST) MIME-Version: 1.0 Received: by 10.200.43.147 with HTTP; Tue, 8 Nov 2016 01:15:47 -0800 (PST) In-Reply-To: References: From: Jani Nikula Date: Tue, 8 Nov 2016 11:15:47 +0200 Message-ID: Subject: Re: Notmuch dev workflow: applying patches to local trees To: Matt Armstrong Cc: Notmuch Mail Content-Type: text/plain; charset=UTF-8 X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Nov 2016 09:15:51 -0000 On Tue, Nov 8, 2016 at 1:16 AM, Matt Armstrong wrote: > I'm not experienced with managing patches via email on this list, > especially when it comes to applying patches sent out for review and > testing. Is there a documented best practice? Not sure about best practice, but this works for me: M-x cd RET /path/to/repo RET Apply a single patch in show mode: | git am RET Apply all expanded patch messages in a thread in show mode: C-u | git am RET You do have to setup the branch yourself in advance. > Ideally, I'd like a "dwim" command that does something reasonable, such > as take messages from the current thread and apply the patch series to a > new/pristine git branch in my local repo. You can also write your own shell script that does the right things when you pipe patch(es) to it. BR, Jani.