From: keramida@ceid.upatras.gr (Giorgos Keramidas)
To: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: ding@gnus.org, emacs-devel@gnu.org
Subject: Re: Emacs trunk and Gnus master are fully sync'd now
Date: Tue, 02 Jul 2013 18:52:40 +0200 [thread overview]
Message-ID: <67um8rzju4ykdj.fsf@saturn.laptop> (raw)
In-Reply-To: <b4mip0tjldi.fsf@jpl.org> (Katsumi Yamaoka's message of "Tue, 02 Jul 2013 19:40:09 +0900")
On Tue, 02 Jul 2013 19:40:09 +0900, Katsumi Yamaoka <yamaoka@jpl.org> wrote:
> Hi,
> I've merged to the Emacs Bzr trunk the changes that were made in
> the Gnus Git master but haven't yet been merged since February 2012.
> The changes are for mainly the nnimap functions. There might be
> some unresolved problems; but it is the very reason to open to
> many testers and developers. I heard it works fine more or less
> (I'm not an IMAP user). If you meet with a problem, take a look
> at the past discussions in the ding list and try to improve it.
One of the differences I see with the latest version of Gnus is that
accessing Gmail over imap+tls now downloads a lot more data for the
groups:
% nnimap read 0k from imap.gmail.com (initial sync of 129 groups; please wait)
% nnimap read 27k from imap.gmail.com (initial sync of 129 groups; please wait)
% nnimap read 123k from imap.gmail.com (initial sync of 129 groups; please wait)
% [...]
% nnimap read 21163k from imap.gmail.com (initial sync of 129 groups; please wait)
% nnimap read 21243k from imap.gmail.com (initial sync of 129 groups; please wait)
% nnimap read 21272k from imap.gmail.com (initial sync of 129 groups; please wait) [3 times]
The next time I start Gnus it tries to do an 'initial sync of 129
groups' all over again, and this delays startup time a lot.
This may be an artifact of my local configuration. I'll try to clean it
up and post a copy here.
next prev parent reply other threads:[~2013-07-02 16:52 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-02 10:40 Katsumi Yamaoka
2013-07-02 16:52 ` Giorgos Keramidas [this message]
2013-07-06 15:21 ` Lars Ingebrigtsen
2013-07-06 15:44 ` David Engster
2013-07-06 18:45 ` David Engster
2013-07-06 20:03 ` David Engster
2013-07-07 13:27 ` Giorgos Keramidas
2013-07-07 13:24 ` Giorgos Keramidas
2013-07-07 19:51 ` David Engster
2013-07-08 13:16 ` Giorgos Keramidas
2013-07-08 18:24 ` David Engster
2013-07-09 11:08 ` Giorgos Keramidas
2013-07-09 15:34 ` David Engster
2013-07-09 18:16 ` Giorgos Keramidas
2013-07-09 19:33 ` David Engster
2013-07-09 19:39 ` Ted Zlatanov
2013-07-09 20:41 ` Giorgos Keramidas
2013-07-09 21:42 ` David Engster
2013-07-10 15:32 ` Ted Zlatanov
2013-07-10 19:17 ` David Engster
2013-07-11 17:12 ` Giorgos Keramidas
2013-07-18 13:31 ` Lars Magne Ingebrigtsen
2013-07-18 15:42 ` Giorgos Keramidas
2013-07-18 16:55 ` David Engster
2013-07-18 17:15 ` Giorgos Keramidas
2013-07-30 14:56 ` Lars Magne Ingebrigtsen
2013-07-30 19:58 ` Giorgos Keramidas
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=67um8rzju4ykdj.fsf@saturn.laptop \
--to=keramida@ceid.upatras.gr \
--cc=ding@gnus.org \
--cc=emacs-devel@gnu.org \
--cc=yamaoka@jpl.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).