From: Gaute Hope <eg@gaute.vetsj.com>
To: Sup developer discussion <sup-devel@rubyforge.org>
Cc: Horacio Sanson <hsanson@gmail.com>
Subject: Re: [sup-devel] Gmail source sync back.
Date: Thu, 22 Aug 2013 14:35:28 +0200 [thread overview]
Message-ID: <52160590.4040502@gaute.vetsj.com> (raw)
In-Reply-To: <51F6CA0B.7090406@gaute.vetsj.com>
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
prev parent reply other threads:[~2013-08-22 12:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-03 9:44 Horacio Sanson
2013-07-04 20:38 ` Matthieu Rakotojaona
2013-07-29 19:37 ` Gaute Hope
2013-07-29 19:48 ` Gaute Hope
2013-07-29 20:01 ` Gaute Hope
2013-08-22 12:35 ` Gaute Hope [this message]
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=52160590.4040502@gaute.vetsj.com \
--to=eg@gaute.vetsj.com \
--cc=hsanson@gmail.com \
--cc=sup-devel@rubyforge.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