From: David Engster <deng@randomsample.de>
To: ding@gnus.org
Subject: Re: Snappy low-bandwidth nnimap, part II
Date: Wed, 05 Jun 2013 18:46:55 +0200 [thread overview]
Message-ID: <87txlcijy8.fsf@randomsample.de> (raw)
In-Reply-To: <87li71x1cc.fsf@randomsample.de> (David Engster's message of "Sun, 26 May 2013 16:28:03 +0200")
David Engster writes:
> So the fix is pretty simple: Keep empty unexist ranges in the group's
> info. The attached patch does that, but I'm not sure if this really is
> the best solution, or if maybe this shouldn't be better fixed in
> nnimap-retrieve-group-data-early?
I've used this change for a while and it seems to work fine, so I've
pushed it. Of course, if someone has a nicer solution, feel free to
change it.
-David
next prev parent reply other threads:[~2013-06-05 16:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-26 14:28 David Engster
2013-06-05 16:46 ` David Engster [this message]
2013-06-06 14:36 ` Ted Zlatanov
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=87txlcijy8.fsf@randomsample.de \
--to=deng@randomsample.de \
--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).