Return-Path: X-Original-To: notmuch@notmuchmail.org Delivered-To: notmuch@notmuchmail.org Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id 2EA9D429E28 for ; Wed, 4 Sep 2013 02:50:15 -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 1RuTiAZ6VuMC for ; Wed, 4 Sep 2013 02:50:10 -0700 (PDT) Received: from server.belohrad.ch (static-212-101-19-163.adsl.solnet.ch [212.101.19.163]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by olra.theworths.org (Postfix) with ESMTPS id 53635431FDA for ; Wed, 4 Sep 2013 02:50:10 -0700 (PDT) Received: from beesknees.cern.ch.belohrad.ch (beesknees.cern.ch [137.138.197.99]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: david) by server.belohrad.ch (Postfix) with ESMTPSA id 63EEB2C0055; Wed, 4 Sep 2013 11:50:23 +0200 (CEST) From: David Belohrad To: David Bremner , notmuch mailing list Subject: Re: proposal to remove contrib/notmuch-vim and contrib/notmuch-deliver In-Reply-To: <87ioygrkhj.fsf@zancas.localnet> References: <87ioygrkhj.fsf@zancas.localnet> User-Agent: Notmuch/0.15.2+73~g1c450ec (http://notmuchmail.org) Emacs/23.4.1 (x86_64-pc-linux-gnu) Date: Wed, 04 Sep 2013 11:50:05 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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: Wed, 04 Sep 2013 09:50:15 -0000 is actually someone using notmuch deliver? i was thinking to use is as my 'implementation' of emailing uses remote access via SSH. This one is considerably slower (especially when slow uplink) than local access and hence if notmuch-deliver would be in a shape, that would spare at least some time when 'notmuch new' is invoked from remote. i agree however that 'notmuch new' could be scheduled at some interval, notmuch-deliver would be much clearer solution. .d. David Bremner writes: > Hi; > > Both are superceded by code in the main tree, and should probably not be > shipped in the next release. I suppose there are some packagers > packaging contrib/notmuch-deliver, but they will have to adapt at some > point anyway. > > Comments? > > d > _______________________________________________ > notmuch mailing list > notmuch@notmuchmail.org > http://notmuchmail.org/mailman/listinfo/notmuch