From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <dimidd@gmail.com>
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on dcvr.yhbt.net
X-Spam-Level: 
X-Spam-ASN: AS3215 2.6.0.0/16
X-Spam-Status: No, score=-3.2 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS
	shortcircuit=no autolearn=ham autolearn_force=no version=3.4.0
Received: from mail-ua0-x233.google.com (mail-ua0-x233.google.com [IPv6:2607:f8b0:400c:c08::233])
	(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
	(No client certificate requested)
	by dcvr.yhbt.net (Postfix) with ESMTPS id 7CD531F576;
	Thu, 25 Jan 2018 08:17:26 +0000 (UTC)
Received: by mail-ua0-x233.google.com with SMTP id e25so2144714uan.5;
        Thu, 25 Jan 2018 00:17:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20161025;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :cc;
        bh=/+HmKJFeMB79GCnCM6qYl7KGwsfJnHGKh90ICJg7qjA=;
        b=Q/BcmCeIjW6dK90OI44BB730KaUY09xwp9bzAA+nfep+VmY3LPHaVx4tp9Ct+MrKsq
         gild4OfNFw78C7C/XQ6JI3+HeC8S+b5qkPgfAEjL8Y1CobDxvPdX5GjWfSLVt+HmYTPG
         ip1/UikbG2KgWKxy68NWMwNb3NeMEMlofhet/h3eLZCAvXqXP/FELQT6cIGH/dnOSom2
         vJO2328kGlzDcVMDxjzixPNadyRWBV1qGcqP+MxhJUQQOeEViR8Hm6x69EeRSRiSCbqY
         EJoWYd/Fu9QQXOQybmQ+c+W6QN0SoEHKqrlaAWD61wTwtbv/iViTB+gjhC7f+cw4qK0Z
         ELzg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-gm-message-state:mime-version:in-reply-to:references:from:date
         :message-id:subject:to:cc;
        bh=/+HmKJFeMB79GCnCM6qYl7KGwsfJnHGKh90ICJg7qjA=;
        b=Ykem2C38bSPz7Yfow8YlgEVlw25EUGGyag/pzkBZt0VW52rmT03p8HIDDGaC8Y0vPA
         34c9JkmVQAuEoe8OtVm9QjqTGiEse1kQw2zmS4Ti03NlQ9lRR7ZsHOl0IUroCSV3qero
         bH7QldC/YcTR4JjSgxBCntzGt7lx3TWTqvcUPb0YuzrH4ay3vCFxNrhsMronysEVb4cS
         dH2C8vxuv8oXyl/xBbmxgIpgvrDos5agPF+rAmNjPd+NApZjHF7wyA92YPkRUXPJUijQ
         fr1PURlIo+re3aeNKnlFwXP2phNN9hZ3CLS0vOMD72x7XCr3bnSpB8aoO9V8WlF7B2BA
         ikoQ==
X-Gm-Message-State: AKwxytc1SB6xdQlXT9Hlcq7zjw2Ll/W8nC1sOStymGNXeXTKruO0kfIl
	WwCJdGkIKPte+HMeT6yNEm0Ega78jymENjNSI6I=
X-Google-Smtp-Source: AH8x224ISQh2c/XUn8V4bfTNRjD9Y/QwDkwMKuEyWGEI9rha6TbGBZaoIggj8J1bWA7VLKvIUreGq06KcLs0TcJIJPw=
X-Received: by 10.176.8.79 with SMTP id b15mr6641646uaf.51.1516868245275; Thu,
 25 Jan 2018 00:17:25 -0800 (PST)
MIME-Version: 1.0
Received: by 10.176.21.2 with HTTP; Thu, 25 Jan 2018 00:16:44 -0800 (PST)
In-Reply-To: <20180124224932.GA13304@starla>
References: <CANKvuDf7esPfy3eQ0B8aQjg4sTYTcxR_LNNWeDBcENFwmyC_3g@mail.gmail.com>
 <20180121234911.GA29238@whir> <CANKvuDcS4_VJMiSxnHdUA+7sdVdeCxkp_L8+re_Z3D=W9-ep_A@mail.gmail.com>
 <CANKvuDdpnbZdp-L1OQBhF5pHSxukRuO_DfdnvVm1cqxXrVFkug@mail.gmail.com>
 <20180123220303.GA7222@80x24.org> <CANKvuDeBhLXMwJeP1gD=7myXH=7_WNJmmXTAg0HMR1=qzFruGw@mail.gmail.com>
 <20180124191837.GA15414@starla> <CANKvuDeZD7k61AZDHZffeUsm_7U-yO+OUuxc3PpB1oSg=mU_7A@mail.gmail.com>
 <20180124224932.GA13304@starla>
From: Dimid Duchovny <dimidd@gmail.com>
Date: Thu, 25 Jan 2018 10:16:44 +0200
Message-ID: <CANKvuDdmsNpZ4L9j3tB3YuXFR1SYCEhr1rAaX-D8renqm79prQ@mail.gmail.com>
Subject: Re: Feature Request: thread grouping
To: Eric Wong <e@80x24.org>
Cc: msgthr-public <msgthr-public@80x24.org>
Content-Type: text/plain; charset="UTF-8"
List-Id: <msgthr-public.80x24.org>

2018-01-25 0:49 GMT+02:00 Eric Wong <e@80x24.org>:
> Dimid Duchovny <dimidd@gmail.com> wrote:
>> > Can you also add documentation for this feature so I can make a
>> > release?  Thanks again.
>>
>> Sure, let me know if it's clear enough:
>> https://github.com/dimidd/msgthr/commit/6a1d06abc6c42e504a83dca4420c1d5ef39f09d2.patch
>
> Thanks, that's fine and I've pushed to 80x24.org/msgthr.git
> I noticed you're also working on a new lca branch, should we
> wait for that, or are you good with things as-is?

Thanks, I'm  good. The lca branch is intended for a POC of my actual use case,
Lowest Common Ancestor in email threads.
It has another test for the add_child callback. It's a rather specific
and complex test, so I've put it in a separate branch.
That said, feel free to merge it as you see fit.

> Also, if you want, you can also write some text for release
> announcement which will be read by ruby-talk (just reply here
> with the text).  Thanks.

Hmmm, I wasn't thinking about an announcement for such a minor change.
Could you write one?