From: Tomi Ollila <tomi.ollila@iki.fi>
To: Austin Clements <amdragon@MIT.EDU>, notmuch@notmuchmail.org
Subject: Re: [PATCH v2 0/5] Synchronize maildir flags in new/
Date: Sun, 10 Jun 2012 11:32:08 +0300 [thread overview]
Message-ID: <m2txyjr2if.fsf@guru.guru-group.fi> (raw)
In-Reply-To: <1339269258-3542-1-git-send-email-amdragon@mit.edu>
On Sat, Jun 09 2012, Austin Clements <amdragon@MIT.EDU> wrote:
> v2 hopefully addresses Jani's comments about v1's commit messages. It
> also adds a news patch.
LGTM.
Tomi
next prev parent reply other threads:[~2012-06-10 8:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-03 16:57 [PATCH 0/4] Synchronize maildir flags in new/ Austin Clements
2012-06-03 16:57 ` [PATCH 1/4] test: Add broken test for tag synchronization on files delivered to new/ Austin Clements
2012-06-04 7:10 ` Jani Nikula
2012-06-09 19:02 ` Austin Clements
2012-06-03 16:57 ` [PATCH 2/4] lib: Move _filename_is_in_maildir Austin Clements
2012-06-03 16:57 ` [PATCH 3/4] lib: Only synchronize maildir flags for messages in maildirs Austin Clements
2012-06-04 7:01 ` Jani Nikula
2012-06-03 16:57 ` [PATCH 4/4] lib: Treat messages in new/ as maildir messages with no flags set Austin Clements
2012-06-04 7:08 ` Jani Nikula
2012-06-09 19:14 ` [PATCH v2 0/5] Synchronize maildir flags in new/ Austin Clements
2012-06-09 19:14 ` [PATCH v2 1/5] test: Add broken test for tag synchronization on files delivered to new/ Austin Clements
2012-06-09 19:14 ` [PATCH v2 2/5] lib: Move _filename_is_in_maildir Austin Clements
2012-06-09 19:14 ` [PATCH v2 3/5] lib: Only synchronize maildir flags for messages in maildirs Austin Clements
2012-06-09 19:14 ` [PATCH v2 4/5] lib: Treat messages in new/ as maildir messages with no flags set Austin Clements
2012-06-09 19:14 ` [PATCH v2 5/5] News for updated maildir sync semantics Austin Clements
2012-06-10 8:32 ` Tomi Ollila [this message]
2012-06-10 18:06 ` [PATCH v2 0/5] Synchronize maildir flags in new/ Jani Nikula
2012-06-10 23:20 ` David Bremner
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=m2txyjr2if.fsf@guru.guru-group.fi \
--to=tomi.ollila@iki.fi \
--cc=amdragon@MIT.EDU \
--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).