From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <eg@gaute.vetsj.com>
Received: from [192.168.1.207] (c4C8F5BC1.dhcp.as2116.net. [193.91.143.76])
        by mx.google.com with ESMTPSA id q5sm4896875lbe.10.1969.12.31.16.00.00
        (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
        Thu, 22 Aug 2013 05:36:29 -0700 (PDT)
Message-ID: <52160590.4040502@gaute.vetsj.com>
Date: Thu, 22 Aug 2013 14:35:28 +0200
From: Gaute Hope <eg@gaute.vetsj.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130806 Thunderbird/17.0.8
MIME-Version: 1.0
To: Sup developer discussion <sup-devel@rubyforge.org>
CC: Horacio Sanson <hsanson@gmail.com>
Subject: Re: [sup-devel] Gmail source sync back.
References: <CAHWBo_bRwKArh7nLQ8EMWdWvBV_kRGT=NqDU=Z69pTY+fNpMUQ@mail.gmail.com> <51F6CA0B.7090406@gaute.vetsj.com>
In-Reply-To: <51F6CA0B.7090406@gaute.vetsj.com>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

On 03. juli 2013 11:44, Horacio Sanson wrote:

Hi,

You should use the :update flag like the maildir-sync branch does for
messages that have changed, that way it is easier to determine whether
the UpdateManager should emit a signal (even if the message already exists).

Cheers, Gaute