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 9358F4196F2 for ; Wed, 14 Apr 2010 02:52:56 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: -0.5 X-Spam-Level: X-Spam-Status: No, score=-0.5 tagged_above=-999 required=5 tests=[BAYES_05=-0.5] autolearn=ham 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 mlBF6YYVAHU0 for ; Wed, 14 Apr 2010 02:52:55 -0700 (PDT) Received: from homiemail-a18.g.dreamhost.com (caiajhbdcaib.dreamhost.com [208.97.132.81]) by olra.theworths.org (Postfix) with ESMTP id B6F8E431FC1 for ; Wed, 14 Apr 2010 02:52:55 -0700 (PDT) Received: from sspaeth.de (unknown [195.190.188.219]) by homiemail-a18.g.dreamhost.com (Postfix) with ESMTPA id B6DCB250065; Wed, 14 Apr 2010 02:52:53 -0700 (PDT) Received: by sspaeth.de (sSMTP sendmail emulation); Wed, 14 Apr 2010 11:52:50 +0200 From: "Sebastian Spaeth" To: David Edmondson , Notmuch developer list Subject: Re: [PATCH 13/13] notmuch.el: Add a function to insert a notmuch user-agent header In-Reply-To: <87r5mibhr7.fsf@ut.hh.sledj.net> References: <87bpdnl02k.fsf@yoom.home.cworth.org> <1271230685-8478-1-git-send-email-Sebastian@SSpaeth.de> <87r5mibhr7.fsf@ut.hh.sledj.net> Date: Wed, 14 Apr 2010 11:52:50 +0200 Message-ID: <87k4sa9x8t.fsf@SSpaeth.de> User-Agent: notmuch version 0.1-107-g553feae (Emacs 23.1.1/x86_64-pc-linux-gnu) 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, 14 Apr 2010 09:52:56 -0000 On 2010-04-14, David Edmondson wrote: > This really should be done with `define-mail-user-agent' and associated > paraphernalia. Which might be correct but beyond what I can provide :). So, either we take this and get a followup patch, or someone improves it, or we drop it. Sebastian