log libpurple/connection.c @ 21728:86f62b1e2a5a

age author description
Sat, 01 Dec 2007 23:42:21 +0000 Will Thompson Remove dead code.
Wed, 14 Nov 2007 04:52:45 +0000 Daniel Atallah Register the correct number of values for the "connection-error" signal.
Sun, 11 Nov 2007 21:37:39 +0000 Will Thompson I don't think that incorrect passwords can be helpfully distinguished from
Sun, 11 Nov 2007 21:22:12 +0000 Will Thompson Consensus on #pidgin is that certificate errors and AUTHENTICATION_IMPOSSIBLE
Sun, 11 Nov 2007 19:09:49 +0000 Will Thompson Add PURPLE_CONNECTION_ERROR_{INVALID_USERNAME,INCORRECT_PASSWORD}, to be used
Sat, 10 Nov 2007 12:10:04 +0000 Will Thompson propagate from branch 'im.pidgin.pidgin' (head d8103be97302efb404e2f6922925f661c807ad23)
Wed, 24 Oct 2007 17:33:12 +0000 Will Thompson I figured a signal firing on a connection error would be useful.
Sun, 14 Oct 2007 21:08:42 +0000 Will Thompson Rename:
Sun, 14 Oct 2007 12:19:20 +0000 Will Thompson rlaager suggested using the last element of the PurpleDisconnectReason enum
Sat, 03 Nov 2007 16:19:50 +0000 Nathan Walp Since the XMPP PurpleConnection is created before we know we need a password,
Wed, 10 Oct 2007 15:16:20 +0000 Will Thompson Clarify the documentation of the return value of
Tue, 09 Oct 2007 15:03:48 +0000 Will Thompson datallah pointed out that using g_return_if_fail() is preferable to
Tue, 09 Oct 2007 13:25:47 +0000 Will Thompson rlaager pointed out that purple_connection_error_reason should be setting
Sat, 06 Oct 2007 12:05:22 +0000 Will Thompson Split the "you don't have SSL support" meaning of
Tue, 02 Oct 2007 19:17:34 +0000 Will Thompson I missed a PURPLE_REASON_INVALID_USERNAME.