# HG changeset patch
# User Will Thompson <will.thompson@collabora.co.uk>
# Date 1190149948 0
# Node ID ed4c1053c3da93e92fa445acb1524e5855977f8a
# Parent  94062344397c8e92846f131322c53bb231a71861
Add PURPLE_REASON_INVALID_USERNAME, which should go away as soon as there's
some hook for prpls to validate the account settings before connecting.

diff -r 94062344397c -r ed4c1053c3da libpurple/connection.h
--- a/libpurple/connection.h	Tue Sep 18 16:39:48 2007 +0000
+++ b/libpurple/connection.h	Tue Sep 18 21:12:28 2007 +0000
@@ -71,6 +71,13 @@
 	 */
 	PURPLE_REASON_NAME_IN_USE,
 
+	/** The username for the account isn't valid.
+	 *  @todo This reason really shouldn't be necessary.  Usernames and
+	 *        other account preferences should be validated when the
+	 *        account is created.
+	 */
+	PURPLE_REASON_INVALID_USERNAME,
+
 	/** The server did not provide a SSL certificate. */
 	PURPLE_REASON_CERT_NOT_PROVIDED,
 	/** The server's SSL certificate could not be trusted. */