From: Frank Schmitt <ich@frank-schmitt.net>
Subject: Re: [PATCH] nnimap performance improvement for large or old groups
Date: Wed, 15 Mar 2006 11:32:12 +0100 [thread overview]
Message-ID: <m33bhkt2vn.fsf@mid.gehheimdienst.de> (raw)
In-Reply-To: <jasbqwkbl0d.fsf@latte.josefsson.org>
Simon Josefsson <jas@extundo.com> writes:
> There are some subtle situations where a message is marked unseen on
> the server (by another client), which should be propagated back into
> gnus, and also when an article is removed.
>
> But it looks OK to me. So if nobody complains, let's move it to v5-10
> in 3 months.
I don't complain, I praise. I love it!
--
Did you ever realize how much text fits in eighty columns? If you now consider
that a signature usually consists of up to four lines, this gives you enough
space to spread a tremendous amount of information with your messages. So seize
this opportunity and don't waste your signature with bullshit nobody will read.
next prev parent reply other threads:[~2006-03-15 10:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-03 1:38 Daniel Pittman
2006-03-03 9:34 ` Simon Josefsson
2006-03-04 0:00 ` Daniel Pittman
2006-03-05 22:10 ` Simon Josefsson
2006-03-15 10:32 ` Frank Schmitt [this message]
2006-03-30 18:37 ` Wes Hardaker
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=m33bhkt2vn.fsf@mid.gehheimdienst.de \
--to=ich@frank-schmitt.net \
/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).