From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id C4D9F431FBD for ; Sat, 12 Apr 2014 08:58:42 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: 0 X-Spam-Level: X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none] autolearn=disabled Received: from olra.theworths.org ([127.0.0.1]) by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qa1KrGASEnv4 for ; Sat, 12 Apr 2014 08:58:38 -0700 (PDT) Received: from yantan.tethera.net (yantan.tethera.net [199.188.72.155]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by olra.theworths.org (Postfix) with ESMTPS id BCE06431FBC for ; Sat, 12 Apr 2014 08:58:38 -0700 (PDT) Received: from remotemail by yantan.tethera.net with local (Exim 4.80) (envelope-from ) id 1WZ0K9-00048N-4R; Sat, 12 Apr 2014 12:58:33 -0300 Received: (nullmailer pid 1288 invoked by uid 1000); Sat, 12 Apr 2014 15:58:29 -0000 From: David Bremner To: David Mazieres expires 2014-07-10 PDT , Gaute Hope Subject: Re: [PATCH] Add configurable changed tag to messages that have been changed on disk In-Reply-To: <877g6v3lb9.fsf@ta.scs.stanford.edu> References: <1396800683-9164-1-git-send-email-eg@gaute.vetsj.com> <87wqf2gqig.fsf@ta.scs.stanford.edu> <1397140962-sup-6514@qwerzila> <87wqexnqvb.fsf@ta.scs.stanford.edu> <87k3aw5dj5.fsf@zancas.localnet> <877g6v3lb9.fsf@ta.scs.stanford.edu> User-Agent: Notmuch/0.17+180~g8977b1a (http://notmuchmail.org) Emacs/24.3.1 (x86_64-pc-linux-gnu) Date: Sat, 12 Apr 2014 12:58:29 -0300 Message-ID: <87mwfq4k0q.fsf@zancas.localnet> MIME-Version: 1.0 Content-Type: text/plain Cc: notmuch X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.13 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: Sat, 12 Apr 2014 15:58:42 -0000 dm-list-email-notmuch@scs.stanford.edu writes: > > As far as updating the test suite, etc., it's almost certain that the > core notmuch developers would be unsatisfied with whatever I've done, > since the code base is very clean and has a very uniform style. So when > I say I'd want some "indication that such a change could be upstreamed," > I mean more specifically that someone would be willing to shepherd the > process of getting the code into shape. > I think it depends on your definition of shepherd. If it means review your patches and tell you what needs to be done, then we can probably handle that. Things tend to stall if the patch proposer loses interest after the first review, so we're pretty far from "fire and forget". I'd like to hear one or two more opinions from regular contributors before I say "yes, this is something we want to do." cheers, d