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 30553431FAF for ; Tue, 3 Jul 2012 19:00:01 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: -0.799 X-Spam-Level: X-Spam-Status: No, score=-0.799 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7] 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 z9YbuXoMZAoX for ; Tue, 3 Jul 2012 18:59:59 -0700 (PDT) Received: from mail-gh0-f181.google.com (mail-gh0-f181.google.com [209.85.160.181]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by olra.theworths.org (Postfix) with ESMTPS id 22E6D431FAE for ; Tue, 3 Jul 2012 18:59:59 -0700 (PDT) Received: by ghbz13 with SMTP id z13so7825188ghb.26 for ; Tue, 03 Jul 2012 18:59:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:message-id:from:to:cc:subject:in-reply-to:references :mime-version:content-type:content-disposition :content-transfer-encoding; bh=sQPt2vi55FlsamtfihEH1v7Tl2NPoZJlZcpCIWK8drg=; b=eOcGgeo6TUDiTQ8IKStmjxcDe4KTFU7LY9RCRTyxam2VxMQhYk6VG0q3HuZgP/OfXC xeFKDMWEeito0w/8cMWSMuqiqLxe4J7h2Yn+TNJedx3TgmK4yJ0sgqcKelv8amHgul54 /v+QoyGjxJvg/NGAL2EJWmjsGMK5IZ9u9HyiPISfTea9l0HkUCp5z3LLskTgvl2IdTOV BSB22B64cfxsKxwE4nKfHFD2VuRxP7QKVLzRReYoiAbIQchd+sOmUMssYvc4/wFwViR9 jE1i8eboP23+X8OZDIRL2FMk53URVWAdtu0A+rhTty9m36KHcPRzAhATJEcpcL86tIkb f1LA== Received: by 10.68.194.201 with SMTP id hy9mr4165191pbc.69.1341367197232; Tue, 03 Jul 2012 18:59:57 -0700 (PDT) Received: from localhost (215.42.233.220.static.exetel.com.au. [220.233.42.215]) by mx.google.com with ESMTPS id of1sm16662864pbb.15.2012.07.03.18.59.54 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 03 Jul 2012 18:59:56 -0700 (PDT) Date: Wed, 4 Jul 2012 11:59:51 +1000 Message-ID: <20120704115951.GC2342@hili.localdomain> From: Peter Wang To: Jameson Graef Rollins Subject: Re: [PATCH 2/3] show: output Reply-To headers In-Reply-To: <87vci471tw.fsf@servo.finestructure.net> References: <1340508470-16606-1-git-send-email-novalazy@gmail.com> <1340508470-16606-2-git-send-email-novalazy@gmail.com> <87vci471tw.fsf@servo.finestructure.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit Cc: notmuch@notmuchmail.org 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 Jul 2012 02:00:01 -0000 On Tue, 03 Jul 2012 18:27:23 -0700, Jameson Graef Rollins wrote: > On Sat, Jun 23 2012, Peter Wang wrote: > > Output Reply-To headers when present in a message. > > These were missing in text and json output formats. > > I don't see why the Reply-To header is needed, given that we are > constructing reply templates, but I guess if someone thinks it's needed > I don't see much harm in including it. I want to see what the sender intended, before hitting reply. Peter