From: Dimid Duchovny <dimidd@gmail.com>
To: Eric Wong <e@80x24.org>
Cc: msgthr-public <msgthr-public@80x24.org>
Subject: Re: Feature Request: thread grouping
Date: Thu, 25 Jan 2018 10:16:44 +0200 [thread overview]
Message-ID: <CANKvuDdmsNpZ4L9j3tB3YuXFR1SYCEhr1rAaX-D8renqm79prQ@mail.gmail.com> (raw)
In-Reply-To: <20180124224932.GA13304@starla>
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?
next prev parent reply other threads:[~2018-01-25 8:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-21 9:40 Feature Request: thread grouping Dimid Duchovny
2018-01-21 23:49 ` Eric Wong
2018-01-23 21:04 ` Dimid Duchovny
2018-01-23 21:12 ` Dimid Duchovny
2018-01-23 22:03 ` Eric Wong
2018-01-24 10:28 ` Dimid Duchovny
2018-01-24 19:18 ` Eric Wong
2018-01-24 21:14 ` Dimid Duchovny
2018-01-24 22:49 ` Eric Wong
2018-01-25 8:16 ` Dimid Duchovny [this message]
2018-01-25 8:38 ` Eric Wong
2018-02-08 13:06 ` Dimid Duchovny
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://80x24.org/msgthr/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CANKvuDdmsNpZ4L9j3tB3YuXFR1SYCEhr1rAaX-D8renqm79prQ@mail.gmail.com \
--to=dimidd@gmail.com \
--cc=e@80x24.org \
--cc=msgthr-public@80x24.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/msgthr.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).