Bug 730743 - Add an option to disable sender's photo search at gravatar.com
Bug 730110 - Search results include also last email looked at
Bug 729905 - [external-editor] Mark composer changed after message body set
Bug 729963 - Include SIP, IM and TEL while merging contacts + Allow to select GivenName, FN
Bug 729667 - Create Folder window is much too short
Bug 729519 - [Composer] Do not show 'Untitled Message' in Discard question
Bug 729303 - Default width of Message Filters window is too small
Bug 731082 - Send mail in offline mode should use Outbox folder
Add "Send messages through Outbox folder" option

Users ask from time to time for the old behaviour when the messages
used to be saved through Outbox, rather than the composer being opened
all the time the message is sending. The change is pretty simple,
thus why not to add it.

Note the Outbox is not flushed after sending, the users is responsible
to invoke the Outbox flush on his/her own. This also allows a user
to postpone the message send for later.
Bug 604346 - Ctrl+Enter sends mail without asking confirmation
Bug 730738 - Extra new line at the beginning of the message in Edit as New
Ignore false GObject property change notifications

This is related to bug 698275, which did not cover all cases.
The problem here is that the dconf can in certain situation claim
that everything changed (path "/" changed), which GSettingsBinding
propagates to a GObject property unconditionally and GObject's
property setter (g_object_set_property()) also notifies about
the property change unconditionally, despite the real descendant
property setter properly checks for the value change. After all
these false notifications a callback on "notify" signal is called
and possibly an expensive operation is run.

Checking whether the value really changed helps in performance, for
which were added new e-util functions:
   e_signal_connect_notify()
   e_signal_connect_notify_after()
   e_signal_connect_notify_swapped()
   e_signal_connect_notify_object()
which have the same prototype as their GLib counterparts, but they allow
only "notify::..." signals and they test whether the value really changed
before they call the registered callback.
Properly disconnect signal handlers added with e_signal_connect_notify*()

This is a follow-up for the previous commit, where e_signal_connect_notify*()
functions had been added. Due to a different callback and user data being
attached to the 'notify' signal, the g_signal_handlers_*() functions do not
work properly, thus these e_signal_connect_notify*() functions need
a different way for a signal handler disconnect.

A side-change was done in e-settings-web-view-gtkhtml.c, checking for a real
key change from GSettings.
Ignore false GSettings key change notifications

Similar to GObject::notify, the GSettings::changed can be emitted
even if a key didn't change. It's up to the user (aka evolution)
to test for real changes, thus let's do it. It may have certain
performance positive impact too.
Bug 227536 - Add "Message Location" filter option
Bug 730977 - Online state change received in a dedicated thread
Bug 731321 - Missing custom types when loading .ui definition
Bug 668006 - Crash when dragging column headers of Tasks list
Updated French translation
Bug 540362: [webkit-composer] Use webkit for composer

Merge wip/webkit-composer branch into master.