GDBusMessage: Don't reset serial number when copying

Ryan pointed out that it's safe to do this because we have the
G_DBUS_SEND_MESSAGE_FLAGS_PRESERVE_SERIAL flag and that it simplifies
how filter functions work.

Signed-off-by: David Zeuthen <davidz@redhat.com>

1 files changed, 6 insertions, 6 deletions

diff --git a/gio/gdbusconnection.h b/gio/gdbusconnection.h
index 4e3a80ae0..eb3e0f36b 100644
--- a/gio/gdbusconnection.h
+++ b/gio/gdbusconnection.h
@@ -528,12 +528,12 @@ void             g_dbus_connection_signal_unsubscribe         (GDBusConnection
  *   return copy;
  * }
  * ]|
- * If the returned #GDBusMessage is different from @message and the
- * serial number is unset (e.g. zero), then @message's serial number
- * will be used on the returned message (so in this case the returned
- * message must be unlocked). Additionally, if the returned message
- * cannot be sent on @connection, then a warning is logged to
- * <emphasis>standard error</emphasis>.
+ * If the returned #GDBusMessage is different from @message and cannot
+ * be sent on @connection (it could use features, such as file
+ * descriptors, not compatible with @connection), then a warning is
+ * logged to <emphasis>standard error</emphasis>. Applications can
+ * check this ahead of time using g_dbus_message_to_blob() passing a
+ * #GDBusCapabilityFlags value obtained from @connection.
  *
  * Returns: (transfer full) (allow-none): A #GDBusMessage that will be freed with
  * g_object_unref() or %NULL to drop the message. Passive filter