- Bump server protocol version to 2310, due to the various changes and so

you can use deny link { } blocks if you want to deny older versions than
  this release.

Changes

@@ -2265,3 +2265,6 @@
 - Fix set::ssl::options::no-starttls not being recognized.
 - Fix pointer handling in remote MOTD code, fixing a crash on REHASH
   reported by goldenwolf (#3992).
+- Bump server protocol version to 2310, due to the various changes and so
+  you can use deny link { } blocks if you want to deny older versions than
+  this release.

doc/technical/serverprotocol.html

@@ -76,7 +76,7 @@
 		<hr/>
 		<h1><a name="S1"></a>1 Introduction</h1>
 		<p>This document describes the UnrealIRCd server-to-server protocol as of protocol 2307 (Unreal 3.2.4). 
-		It is currently slightly out of date, as the current protocol is 2309, but that should not matter much.</p>
+		It is currently slightly out of date, as the current protocol is 2310, but that should not matter much.</p>
 		<h2>A word about clocks.</h2>
 		<p>Unreal is very time-dependant. Users and channels, for example, are timestamped, and if server clocks are not synchronized properly, things can go very wrong very fast. See <a href="http://vulnscan.org/UnrealIrcd/faq/#67">http://vulnscan.org/UnrealIrcd/faq/#67</a> for more information on this. Note that there is a slight difference between server time and what is actually reported by the UNIX date command or by the C time() function. Unreal can apply an offset to the real time to create the server time, allowing servers to be virtually synchronized when synchronizing the real clocks is not possible (such as on shell servers).
 			I should make it quite clear that GMT time is used for everything. To be specific, timestamps in unreal are 32-bit integer values (actually, however many bits the time_t type is, which is 32 on 32-bit systems such as x86). This integer value is the number of seconds that have elapsed since Midnight January 1, 1970 GMT (can be referred to as Epoch time in the UNIX world). This means that timezones are no problem, nor is daylight savings time (or whatever your country of choice calls it).</p>
@@ -117,7 +117,8 @@
 		<p>The server.name is the same as that in the remote server's link:: block. When received from unreal servers, this will be the value of that server's me::name. The protocol version is the numeric protocol version (2306 for example), and the protocol flags are the server's compilation flags (described below). These two fields are checked against the deny version {} blocks in the remote server's configuration. A value of 0 for either field prevents deny version{} checking for that field. The server description can be anything. When received from unreal servers, it'll be the value of me::description.</p>
 		<p>The following version numbers have been used previously:</p>
 		<ul>
-			<li>2309 - Unreal 3.2.6, 3.2.7, 3.2.8, 3.2.9</li>
+			<li>2310 - Unreal 3.2.9</li>
+			<li>2309 - Unreal 3.2.6, 3.2.7, 3.2.8</li>
 			<li>2308 - Unreal 3.2.5</li>
 			<li>2307 - Unreal 3.2.4</li>
 			<li>2306 - Unreal 3.2.3</li>

doc/technical/vl.txt

@@ -2,7 +2,8 @@ VL Information (c) 2002 codemastr (Dominick Meglio) [codemastr@unrealircd.com]
 
 Protocol       Version
 ------------------------------------------------------------------------------------------------
-2309           3.2.6, 3.2.7, 3.2.8, 3.2.9
+2310           3.2.9
+2309           3.2.6, 3.2.7, 3.2.8
 2308           3.2.5
 2307           3.2.4
 2306           3.2.3

include/version.h

@@ -48,7 +48,7 @@
  */
 #define UNREAL_VERSION_TIME         201101
 
-#define UnrealProtocol 		2309
+#define UnrealProtocol 		2310
 #define PATCH1  		"3"
 #define PATCH2  		".2"
 #define PATCH3  		".9"