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 D3A3C431FBC for ; Wed, 7 Nov 2012 05:04:48 -0800 (PST) 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 cl1P1QY5nBsr for ; Wed, 7 Nov 2012 05:04:46 -0800 (PST) Received: from guru.guru-group.fi (guru.guru-group.fi [46.183.73.34]) by olra.theworths.org (Postfix) with ESMTP id 8D9BF431FAE for ; Wed, 7 Nov 2012 05:04:46 -0800 (PST) Received: from guru.guru-group.fi (localhost [IPv6:::1]) by guru.guru-group.fi (Postfix) with ESMTP id D2ACF100094; Wed, 7 Nov 2012 15:04:46 +0200 (EET) From: Tomi Ollila To: David Bremner , Michal Nazarewicz Subject: Re: [PATCH] Add NEWS information about Bcc header in JSON output In-Reply-To: <87a9utk42c.fsf@zancas.localnet> References: <877gqihznz.fsf@zancas.localnet> <5d27cfbe8488a03bfc0322c552ecb5d18043afc3.1351526744.git.mina86@mina86.com> <87hapajp6e.fsf@zancas.localnet> <87a9utk42c.fsf@zancas.localnet> User-Agent: Notmuch/0.14+84~g8a199bf (http://notmuchmail.org) Emacs/24.2.1 (x86_64-unknown-linux-gnu) X-Face: HhBM'cA~ MIME-Version: 1.0 Content-Type: text/plain 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, 07 Nov 2012 13:04:49 -0000 On Wed, Nov 07 2012, David Bremner wrote: > Michal Nazarewicz writes: > >> This commit adds a note to the NEWS file about Bcc header now being >> available in the JSON output (and thus in Emacs) which has been >> implemented by commit ffb629cc5d2c2d1505eb5aefcf04fb4d0af6c0c8. > > Hmm. I was about to push this when I realized the next patches which add > In-Reply-To also need a news entry. How about a combinded news entry for > all of the new fields? You basicaly mean like s/Bcc header/Bcc and In-Reply-To headers/ ?? At the same time s/jsonK/json/ change could be made (?) Also, I don't know whether markdown allows the text in backticks (``) be split into 2 lines -- at the end it's me who is going to do final corrections there ;) (luckily that probably changes when more text is added to the sentences. > d Tomi