aboutsummaryrefslogtreecommitdiffstats
path: root/libibex
diff options
context:
space:
mode:
authorJeffrey Stedfast <fejj@ximian.com>2001-08-18 03:02:48 +0800
committerJeffrey Stedfast <fejj@src.gnome.org>2001-08-18 03:02:48 +0800
commit2968652a61a5e69556559c304b9362f049fa1544 (patch)
treedd2059a395838cb6bd63fc300e443860658f5d91 /libibex
parent512423460aae7c2e98fc888e58d171f1bd68dca2 (diff)
downloadgsoc2013-evolution-2968652a61a5e69556559c304b9362f049fa1544.tar
gsoc2013-evolution-2968652a61a5e69556559c304b9362f049fa1544.tar.gz
gsoc2013-evolution-2968652a61a5e69556559c304b9362f049fa1544.tar.bz2
gsoc2013-evolution-2968652a61a5e69556559c304b9362f049fa1544.tar.lz
gsoc2013-evolution-2968652a61a5e69556559c304b9362f049fa1544.tar.xz
gsoc2013-evolution-2968652a61a5e69556559c304b9362f049fa1544.tar.zst
gsoc2013-evolution-2968652a61a5e69556559c304b9362f049fa1544.zip
Start scanning new messages at maxuid + 1 rather than uidval + 1? Maybe
2001-08-17 Jeffrey Stedfast <fejj@ximian.com> * providers/imap/camel-imap-folder.c (imap_update_summary): Start scanning new messages at maxuid + 1 rather than uidval + 1? Maybe I'm missing the logic, but anyways...this might fix bug #5348. svn path=/trunk/; revision=12170
Diffstat (limited to 'libibex')
0 files changed, 0 insertions, 0 deletions