From: James Cloos <cloos@jhcloos.com>
To: ding@gnus.org
Subject: Re: Number of unread articles suddenly incorrect with Exchange 2007
Date: Thu, 14 Oct 2010 13:54:23 -0400 [thread overview]
Message-ID: <m31v7sy80o.fsf@carbon.jhcloos.org> (raw)
In-Reply-To: <m339s828bj.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Thu, 14 Oct 2010 15:49:20 +0200")
I've not debugged it, but am also seeing inaccurate *Group* numbers
again. I'm currently at 12b9276adbac1bd4d472aa16197f4fe4a1179365.
And like Dave reported, this is a regression. The new nnimap used
to get this right, unlike the old nnimap.
The last it worked was before you wrote that you had broken nnimap;
0261fd46d2dd0ee6087bca2abd55cbb0a2b479c3 is known good. That is a
range of 46 commits, so it should take about 6 iterations to narrow
down to the commit which broke the *Group* counts.
Until I finish re-writing how dbmail does an imap LIST, it will be
painful for me to bisect.
Dave (or anyone else): if you want to try a git bisect, you can use
commit 0261fd46 as a known good commit and 12b9276a as a known bad.
The git-bisect(1) man page explains how to use git bisect.
-JimC
--
James Cloos <cloos@jhcloos.com> OpenPGP: 1024D/ED7DAEA6
prev parent reply other threads:[~2010-10-14 17:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-13 13:42 Dave Goldberg
2010-10-13 18:25 ` Lars Magne Ingebrigtsen
2010-10-14 13:00 ` Dave Goldberg
2010-10-14 13:49 ` Lars Magne Ingebrigtsen
2010-10-14 15:18 ` Dave Goldberg
2010-10-14 18:10 ` Lars Magne Ingebrigtsen
2010-10-14 21:08 ` Dave Goldberg
2010-10-14 21:18 ` Lars Magne Ingebrigtsen
2010-10-14 17:54 ` James Cloos [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m31v7sy80o.fsf@carbon.jhcloos.org \
--to=cloos@jhcloos.com \
--cc=ding@gnus.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.
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 NNTP newsgroup(s).