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 3925D431FB6 for ; Mon, 4 Feb 2013 02:39:49 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: -0.698 X-Spam-Level: X-Spam-Status: No, score=-0.698 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=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 usJp0+xPCRjM for ; Mon, 4 Feb 2013 02:39:48 -0800 (PST) Received: from mail-lb0-f169.google.com (mail-lb0-f169.google.com [209.85.217.169]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by olra.theworths.org (Postfix) with ESMTPS id F1B2E431FAE for ; Mon, 4 Feb 2013 02:39:47 -0800 (PST) Received: by mail-lb0-f169.google.com with SMTP id m4so6569592lbo.0 for ; Mon, 04 Feb 2013 02:39:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=LZQRR7999u2s2zLHdrWW6OBVBck+rBTTDEUvUSmA7/c=; b=d/n5oU1+WQF1pgA+FZH/TvJqn9sVn9x+jGKqYYvlbL7ZGojqFn5oeUp3GGmAzkmZ6N Va99uCorti4KiAs6BAfHCbTVmZ4GV03MNP2XydnJQGFaqKy8afxWgK1vhWqQ6QQuN90r FS/SDSZq0mpboZgohQSRx5KKkoUds15lCMkvThqc6Na44Pa1RQfS17dNMjs6wBoZwYaY VAhJoWoGFvWz0OQ2FMVR9eK6l/KdrJRpLjYPo+ksOKd1QJ85JqW/yL3T1ytR9OasTLje Oo4Eh/TGQ0q9eretETiDVw8iyThYz7AfEVwBjKct5lmvbrG36ICqkv4LOp7mOD462bmW z4lg== MIME-Version: 1.0 X-Received: by 10.112.23.136 with SMTP id m8mr8082038lbf.53.1359974384828; Mon, 04 Feb 2013 02:39:44 -0800 (PST) Sender: mnazarewicz@gmail.com Received: by 10.114.99.65 with HTTP; Mon, 4 Feb 2013 02:39:44 -0800 (PST) Received: by 10.114.99.65 with HTTP; Mon, 4 Feb 2013 02:39:44 -0800 (PST) In-Reply-To: <000001ce0161$5da40990$18ec1cb0$@nl> References: <000001cdfcd9$82500f00$86f02d00$@nl> <000001ce0161$5da40990$18ec1cb0$@nl> Date: Mon, 4 Feb 2013 11:39:44 +0100 X-Google-Sender-Auth: 57rVVK4hNkAOjgCZ9gT3QZCOvtA Message-ID: Subject: RE: Reply all - issue From: =?UTF-8?Q?Micha=C5=82_Nazarewicz?= To: Robert Mast Content-Type: multipart/alternative; boundary=e0cb4efe304a1c828704d4e3b659 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: Mon, 04 Feb 2013 10:39:49 -0000 --e0cb4efe304a1c828704d4e3b659 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 2 lut 2013 17:21, "Robert Mast" napisa=C5= =82(a): > So Gmail-threading is still the best I suppose, I strongly disagree. Having said that, as long as it's configurable I obviously won't be blocking your efforts. > Anyone interested in me patching Notmuch, or shall I keep the changes to myself? I was actually wondering that instead of hard coding the logic into notmuch itself, maybe it would be better to provide some sort of "split-thread" and "join-threads" which could than be used by separate tagging tool. To be user-friendly this may require a possibly to search for all ancestors of a given message and possibly an option to sort results topologically which I dunno if notmuch has. --e0cb4efe304a1c828704d4e3b659 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

2 lut 2013 17:21, "Robert Mast" <beheerder@tekenbeetziekten.nl> na= pisa=C5=82(a):
> So Gmail-threading is still the best I suppose,

I strongly disagree. Having said that, as long as it's c= onfigurable I obviously won't be blocking your efforts.

> Anyone interested in me patching Notmuch, or shall I ke= ep the changes to myself?

I was actually wondering that instead of hard coding the log= ic into notmuch itself, maybe it would be better to provide some sort of &q= uot;split-thread" and "join-threads" which could than be use= d by separate tagging tool.

To be user-friendly this may require a possibly to search fo= r all ancestors of a given message and possibly an option to sort results t= opologically which I dunno if notmuch has.

--e0cb4efe304a1c828704d4e3b659--