unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Carl Worth <cworth@cworth.org>
To: Sebastian Spaeth <Sebastian@SSpaeth.de>, notmuch@notmuchmail.org
Subject: Re: Plans for the 0.2 release (this week)
Date: Tue, 13 Apr 2010 09:02:52 -0700	[thread overview]
Message-ID: <87k4sbe3wz.fsf@yoom.home.cworth.org> (raw)
In-Reply-To: <87bpdul72j.fsf@SSpaeth.de>

[-- Attachment #1: Type: text/plain, Size: 1514 bytes --]

On Thu, 08 Apr 2010 09:47:00 +0200, "Sebastian Spaeth" <Sebastian@SSpaeth.de> wrote:
> First of all, thanks for the great work Carl. I have to admit I was
> getting nervous about the backlog of patches, but your recent committing
> binge (you did say your work patterns are bursty :-)) made me very happy.

You're quite welcome. And the big backlog was making me nervous too.

I'm not sure that the backlog has gotten any smaller yet, but I'm really
happy with where things are going. I seem to have created a code hydra,
where every time I merge one patch, people get excited to and send me
three more patches.

> That having said, I am glad to meet your expectation: "I expect people
>  to remind me of their favorite features that haven't been merged..."
>  :-)

Thanks for the very useful list, Sebastian. These are all merged now,
(as mentioned in the replies I've made to the original messages with the
patches).

> >   * Some library additions (move_to_first for the iterators,
> +1!

That one I've got noted on a separate list.

> All the rest souds very good.

I really do need a thread-splitting feature in order to use notmuch as
my feature tracker. A list like the above of "6 trivial patches to
merge" is easy to handle as a single item. I can send a message like
this one saying "I'm done with this list".

But several different people did reply to my original "plans for 0.2"
call for features. So the single thread I have for this in my "notmuch
merge window" search is not doing the trick.

-Carl

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2010-04-13 16:02 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-07 22:12 Plans for the 0.2 release (this week) Carl Worth
2010-04-07 22:23 ` James Westby
2010-04-08 14:34   ` Mike Kelly
2010-04-12 18:27     ` Mike Kelly
2010-04-08  7:47 ` Sebastian Spaeth
2010-04-08 12:21   ` Anthony Towns
2010-04-13 16:02   ` Carl Worth [this message]
2010-04-08  8:13 ` David Edmondson
2010-04-08 14:54   ` Dirk Hohndel
2010-04-08 13:52 ` Jameson Rollins
2010-04-08 14:55   ` Dirk Hohndel
2010-04-13 16:06   ` Carl Worth
2010-04-08 14:03 ` Jameson Rollins
2010-04-08 14:58   ` Dirk Hohndel
2010-04-08 15:21     ` Michal Sojka
2010-04-08 15:57     ` draft handling [was: Re: Plans for the 0.2 release (this week)] Jameson Rollins
2010-04-08 21:28     ` Plans for the 0.2 release (this week) Carl Worth
2010-04-08 21:38       ` Jameson Rollins
2010-04-09  0:22       ` Mike Kelly
2010-04-08 15:30   ` Mike Kelly
2010-04-09  3:22   ` Anthony Towns
2010-04-09  4:25     ` Michal Sojka
2010-04-09 16:21   ` micah anderson
2010-04-08 14:22 ` Michal Sojka
2010-04-09  4:32 ` Michal Sojka
2010-04-09  7:35   ` Sebastian Spaeth
2010-04-09 17:14     ` Dirk Hohndel
2010-04-10  3:06       ` Carl n∅tmuch 䚳 Worth
2010-04-10  4:44         ` Dirk Hohndel
2010-04-10  4:47           ` Dirk Hohndel
2010-04-10 13:05             ` Jameson Rollins
2010-04-10 14:39               ` Dirk Hohndel
2010-04-10  9:02         ` Michal Sojka
2010-04-10 13:06           ` Jameson Rollins
2010-04-10 13:09             ` Jameson Rollins
2010-04-10 14:06             ` Michael Elkins
2010-04-10 19:58             ` Michal Sojka
2010-04-10 13:52         ` Sebastian Spaeth
2010-04-10 13:56           ` Jameson Rollins
2010-04-10 14:41           ` Dirk Hohndel
2010-04-13 17:20 ` Carl Worth

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://notmuchmail.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87k4sbe3wz.fsf@yoom.home.cworth.org \
    --to=cworth@cworth.org \
    --cc=Sebastian@SSpaeth.de \
    --cc=notmuch@notmuchmail.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://yhetil.org/notmuch.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).