From: Eric Wong <firstname.lastname@example.org> To: Dimid Duchovny <email@example.com> Cc: firstname.lastname@example.org Subject: Re: Feature Request: thread grouping Date: Thu, 25 Jan 2018 08:38:36 +0000 Message-ID: <20180125083836.GA3766@80x24.org> (raw) In-Reply-To: <CANKvuDdmsNpZ4L9j3tB3YuXFR1SYCEhr1rAaX-D8renqm79prQ@mail.gmail.com> Dimid Duchovny <email@example.com> wrote: > 2018-01-25 0:49 GMT+02:00 Eric Wong <firstname.lastname@example.org>: > > 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. OK, I will wait until it's more proven. I'm pretty conservative about accepting new features because of support and performance concerns. > > 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? Sure, but I was just thinking you could do a better job introducing it to other people since you wrote it :) I announce all releases of software I intend to support to ruby-talk. I'm sleepy so my English has deteriorated, will wait until tomorrow before releasing + announcement.
next prev parent reply index Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-01-21 9:40 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 2018-01-25 8:38 ` Eric Wong [this message] 2018-02-08 13:06 ` Dimid Duchovny
Reply instructions: You may reply publically 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=20180125083836.GA3766@80x24.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ /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
msgthr user+dev discussion/patches/pulls/bugs/help Archives are clonable: git clone --mirror https://80x24.org/msgthr-public Newsgroups are available over NNTP: nntp://news.public-inbox.org/inbox.comp.lang.ruby.msgthr nntp://ou63pmih66umazou.onion/inbox.comp.lang.ruby.msgthr note: .onion URLs require Tor: https://www.torproject.org/ or Tor2web: https://www.tor2web.org/ AGPL code for this site: git clone https://public-inbox.org/ public-inbox