On Wed 11 Dec 2013 at 10:41:13AM +0100, Oswald Buddenhagen wrote:
> > it makes maintaining parallel branches somewhat difficult
>
> yes, i know. sorry for that. for all i know you are the only one who
> ever maintained a branch (you still do? why? let's talk about it!),
Haha, yes this may well be
commit 2bbd07ec87d81cb7a20aa49344b66d6cfdc4fc78
Author: Oswald Buddenhagen
Date: Wed Dec 11 16:29:02 2013 +0100
adjust comments to new reality
src/sync.c | 11 ---
1 files changed, 4 insertions(+), 7 deletions(-)
diff --git a/src/sync.c b/src/sync.c
index 957188c..4df172c 10064
commit 5a21042e980a4697623eaf5614a1dad0e6fdee23
Author: Oswald Buddenhagen
Date: Wed Dec 11 16:25:30 2013 +0100
ensure sequencing of message propagation and store closing
by putting the message propagation last, d3f634702 uncovered a
long-standing problem: we might have closed
commit c47ee1c8c4bc1961cf7fd665326bfa05504ab0e7
Author: Oswald Buddenhagen
Date: Wed Dec 11 16:13:49 2013 +0100
fix error paths wrt sync drivers, take 3
msgs_copied() was not checked at all, and msgs_flags_set() was doing it
wrong (sync_close() was not checked).
instea
commit 2f0fbcd3068da05056107a88f58c92d75bb213c6
Author: Oswald Buddenhagen
Date: Wed Dec 11 14:30:38 2013 +0100
don't use UID EXPUNGE unless trashing
a simple CLOSE is way more efficient, so use it if no adverse effects
can come from it.
src/drv_imap.c |2 +-
1 files chan
On Tue, Dec 10, 2013 at 11:17:49PM -0600, guns wrote:
> I have noticed that you have reset the master branch of
> http://sourceforge.net/projects/isync/ three times in the last month.
>
three? i don't think so.
i rewrote the history of all branches to retroactively fix a git setup
glitch (and remo
