X-Git-Url: http://dxcluster.net/gitweb/gitweb.cgi?a=blobdiff_plain;f=Changes;h=45c6ea750c07026b127d36c61bd75d4a8469b0d5;hb=19740220d324a319fb868ce34fb7bed7e31dd450;hp=bfb0b248479af4c926473e5a7d2e41853c131040;hpb=934a5db829e43833c5f6c45c8cd9919dcfe734b9;p=spider.git

diff --git a/Changes b/Changes
index bfb0b248..45c6ea75 100644
--- a/Changes
+++ b/Changes
@@ -1,7 +1,46 @@
+18Jul07=======================================================================
+1. Change the meaning of set/isolate. Set/isolate now works in both directions
+in that an isolated node will only have its local config remembered and will
+only be sent this nodes local config. This is exactly equivalent to both
+ends setting set/isolate. If that is already the case then there should be
+no noticeable change. Any extra that the far node sends, over and above its
+local config will now be ignored.
+17Jul07=======================================================================
+1. remove dupefile on startup and on ending the node. Add clear/dupefile
+command to allow people to do it at runtime as well.
+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
+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=======================================================================
+1. fix unwanted dupe notifications if a PC12 comes back in on a loop.
 02Jul07=======================================================================
 1. Add a new command to show the contents of the cmd_cache. This allows those
 people whom develop their own commands to see which version they are using.
 It is called show/cmd_cache (or sh/cmd for short).
+2. Add some extra info to the links command. Show whether a link is isolated
+and also whether it has filters (if applicable) and whether these are
+personalised ('Y') or the default node_filter ('D').
 29Jun07=======================================================================
 1. If a node is set/isolated then make sure that a) pc9x is not advertised
 and b) pc9x is ignored.