fix another possible(?) error on broadcast p92 update

[spider.git] / Changes

diff --git a/Changes b/Changes
index 86432dd566e3e43331699ea67cbde513fba0b79b..f03ffc3e25dc5707473bc3dc10acc23fc1c6d7b7 100644 (file)
--- a/Changes
+++ b/Changes
@@ -1,3 +1,16 @@
+12Jul07=======================================================================
+1. Change disconnection code so that nodes that are no longer routable are
+(all) cleared out.
+2. Add help for sh/band and also allow query of individual band or regions.
+11Jul07=======================================================================
+1. improve speed of sh/c/n
+2. remove all $Id$ strings from cmd tree
+09Jul07=======================================================================
+1. remove check for PC93 from legacy nodes. This will allow PC10s to be
+propagated correctly. Probably.
+08Jul07=======================================================================
+1. put in a temporary fix to the crashing on incoming PC10 talks, whilst I
+try to work out how it is happening.
 06Jul07=======================================================================
 1. re-arrange id checking so that it is more logical and check that config
 records, that can be an hour coming, are not thoughtlessly ignored, thus
@@ -5,6 +18,8 @@ causing nodes to time out.
 2. Make sure that the 'over midnight' distance calculation actually does what
 is required!
 3. Tart up version number reporting in sh/node.
+4. Pass the correct number of parameters in pc93 -> pc12 conversions which
+should stop returning PC12s coming out as SYSOP announces.
 05Jul07=======================================================================
 1. Try to make sure that the node config broadcasts are actually sent...
 03Jul07=======================================================================