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 7698A6DE0941 for ; Mon, 11 Dec 2017 12:51:47 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: 0 X-Spam-Level: X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[AWL=0.011, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-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 pbUA-8uFjO3a for ; Mon, 11 Dec 2017 12:51:46 -0800 (PST) Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197]) by arlo.cworth.org (Postfix) with ESMTPS id EE0206DE0243 for ; Mon, 11 Dec 2017 12:51:45 -0800 (PST) Received: from remotemail by fethera.tethera.net with local (Exim 4.89) (envelope-from ) id 1eOV37-00051K-HF; Mon, 11 Dec 2017 15:51:41 -0500 Received: (nullmailer pid 18772 invoked by uid 1000); Mon, 11 Dec 2017 20:51:38 -0000 From: David Bremner To: "W. Trevor King" Cc: notmuch@notmuchmail.org, Daniel Kahn Gillmor Subject: Re: [PATCH 3/4] nmbug: Auto-checkout in clone if it wouldn't clobber In-Reply-To: <20171211174707.GX19165@valgrind.us> References: <342f60354749e779c30725ad16060b3f1ec2ed38.1507675236.git.wking@tremily.us> <87y3m9mmug.fsf@tethera.net> <20171211174707.GX19165@valgrind.us> Date: Mon, 11 Dec 2017 16:51:38 -0400 Message-ID: <87a7ypdm3p.fsf@tesseract.cs.unb.ca> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.23 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: Mon, 11 Dec 2017 20:51:47 -0000 "W. Trevor King" writes: > On Mon, Dec 11, 2017 at 09:10:47AM -0400, David Bremner wrote: >> Not sure what happened to patch 4/4? > > Ah sorry. My local branch has a commit to bump nmbug's internal > version to 0.3 (see my comments in [1]), but I ended up deciding to > punt that until before the next notmuch release (in case other nmbug > changes landed in the meantime) and forgot to update the denominator. > > Based on [2], perhaps it is now time? Or is [3] likely to land before > the freeze? > I think bumping the version is something reasonable to do during the feature freeze. d