> > I came across it, having been annoyed by the fact that notmuch broke my
> > reading
> > habits by marking messages (in the mutt sense) as seen, which I hadn't
> > really
> > seen yet in mutt. I tried out the patch; it applied and seems to work. What
> > can
> > I do to make it be applied?
On Thu, Sep 15, 2011 at 12:23:17AM +0200, Louis Rilling wrote:
> The intent for the fourth patch (detailed in the commit log) is to allow mutt
> users to keep using the "new" status, as long as notmuch can respect the
> maildir specification.
>
> The third patch implements a test for the new
I came across it, having been annoyed by the fact that notmuch broke my
reading
habits by marking messages (in the mutt sense) as seen, which I hadn't
really
seen yet in mutt. I tried out the patch; it applied and seems to work. What
can
I do to make it be applied? Other than
Daniel writes:
> On Mon, Nov 21, 2011 at 08:41:42PM -0400, David Bremner wrote:
>> I pushed the first two patches in this series; the second two need to be
>> updated for the new "broken test" framework, and reviewed.
>
> And old one... What came of this patch?
>
> I came across it, having been
On Thu, Sep 15, 2011 at 12:23:17AM +0200, Louis Rilling wrote:
The intent for the fourth patch (detailed in the commit log) is to allow mutt
users to keep using the new status, as long as notmuch can respect the
maildir specification.
The third patch implements a test for the new desired
Daniel qu...@hack.org writes:
On Mon, Nov 21, 2011 at 08:41:42PM -0400, David Bremner wrote:
I pushed the first two patches in this series; the second two need to be
updated for the new broken test framework, and reviewed.
And old one... What came of this patch?
I came across it, having
Hello,
Here is the updated series of fixes I have around maildir flags
synchronization. The first two patches are just cleanups that can be applied
independently.
The intent for the fourth patch (detailed in the commit log) is to allow mutt
users to keep using the "new" status, as long as
