- White-space changes

git-svn-id: svn://svn.ircd-hybrid.org/svnroot/ircd-hybrid/branches/8.1.x@2356 82007160-df01-0410-b94d-b575c5fd34c7

8 files changed, 74 insertions, 74 deletions

diff --git a/doc/CIDR.txt b/doc/CIDR.txt
index e17098a..2d357fa 100644
--- a/doc/CIDR.txt
+++ b/doc/CIDR.txt
@@ -274,7 +274,7 @@ Maintainer: BEST
   Note that the FreeBSD whois client has shortcuts for the most commonly
   used whois servers.  "whois -a <INFO>" is the shortcut for ARIN.
 
-  Also note that ARIN is not authoritative for all IP blocks on the 
+  Also note that ARIN is not authoritative for all IP blocks on the
   Internet.  Take for example 212.158.123.66.  A whois query to ARIN
   will return the following information:
 
@@ -306,11 +306,11 @@ country:     GB
 
   This tells us the actual IP block that the query was a part of.
 
-  Other whois servers that you may see blocks referred to are: 
+  Other whois servers that you may see blocks referred to are:
   whois.ripn.net for Russia, whois.apnic.net for Asia, Australia, and
   the Pacific, and whois.6bone.net for IPv6 blocks.
 
 Contributed by Jeremy Chadwick <jdc@best.net>
-Piotr Kucharski <chopin@sgh.waw.pl> 
+Piotr Kucharski <chopin@sgh.waw.pl>
 W. Campbell <wcampbel@botbay.net> and
 Ariel Biener <ariel@fireball.tau.ac.il>
diff --git a/doc/Tao-of-IRC.940110 b/doc/Tao-of-IRC.940110
index fa2f559..d1c2414 100644
--- a/doc/Tao-of-IRC.940110
+++ b/doc/Tao-of-IRC.940110
@@ -10,9 +10,9 @@ and growing and ungrowing. It is there yet not there. It is the source of
 Internet Relay Chat. I do not know the name, thus I will call it the Tao
 of Internet Relay Chat.
 
-If the Tao is great, then the IRC is running ceaselessly. If the IRC is 
-great then the server is running without ever stoping. If the server is 
-great then the client will always be the server. The luser is then pleased 
+If the Tao is great, then the IRC is running ceaselessly. If the IRC is
+great then the server is running without ever stoping. If the server is
+great then the client will always be the server. The luser is then pleased
 and there is Chat in the world.
 
 The Tao of IRC squits far away and connects on returning.
@@ -21,16 +21,16 @@ The Tao of IRC squits far away and connects on returning.
 -----
 The genetic potential of birth, a lot to know, yet unknown.
 
-In the begining there was nothing. 
+In the begining there was nothing.
 
 Out of nothing the Tao gave birth to tolsun.oulu.fi. tolsun gave birth to
-OuluBox. 
+OuluBox.
 
 OuluBox gave birth to rmsg.
 
 rmsg was not Tao, so MUT gave birth to IRC.
 
-No one knows when IRC came into existance, the mighty master WiZ have it 
+No one knows when IRC came into existance, the mighty master WiZ have it
 to be at the end of the eight month in the year of the Dragon.
 
 
@@ -39,17 +39,17 @@ Each channel has its purpose, however humble. Each channel is the Yin and
 Yang of IRC. Each channels has it's place within the IRC.
 
 In the beginning there was only channel 0, thus channel 0 is the soil of
-IRC. 
+IRC.
 
-Channel 1 to channel 10 then was open as the sea. Channel 11 to 999 was the 
+Channel 1 to channel 10 then was open as the sea. Channel 11 to 999 was the
 trees and forests of IRC. Channels above 999 should not be mentioned, and
 channels below 0 were unborn and contained many secrets.
 
-This was not the right Tao, so IRC gave birth to +channels. 
+This was not the right Tao, so IRC gave birth to +channels.
 
 +channels had the yin and yang. Mode does not.
 
-This was not the right Tao still, so IRC gave birth to #channels. 
+This was not the right Tao still, so IRC gave birth to #channels.
 
 #channels have the yin and yang.
 
@@ -59,16 +59,16 @@ Only channel 0 is the right path to Tao, but avoid speaking on channel 0.
 -----
 There was a great dispute among the Broom-Walkers of the Relay. Some of them
 wanted neither yin nor yang. Out of this Eris came into existance. Some of the
-Broom-Walkers then created Eris Free-net. 
+Broom-Walkers then created Eris Free-net.
 
 This was the right Tao.
 
-Kind Gentle and Boring Net was another wrong path to the Tao of Internet Relay 
+Kind Gentle and Boring Net was another wrong path to the Tao of Internet Relay
 Chat.
 
-Some time later there was a quantity of some lusers who wanted to be 
-Broom-Walkers also. The Eris Free Broom-Walkers did not agree with them, 
-thus a new IRC was born. This IRC is called the Undernet. 
+Some time later there was a quantity of some lusers who wanted to be
+Broom-Walkers also. The Eris Free Broom-Walkers did not agree with them,
+thus a new IRC was born. This IRC is called the Undernet.
 
 But this is not the right Tao, either.
 
@@ -80,7 +80,7 @@ This is the very nature of the IRC.
 
 
 -----
-Lusers that do not understand the Tao is always using the yang of Mode on 
+Lusers that do not understand the Tao is always using the yang of Mode on
 their channels. Lusers that do understand the Tao are always using Ignore
 on their channels.
 
@@ -88,7 +88,7 @@ How could this not be so ?
 
 
 -----
-The wise sage luser is told about the Chat and uses it. The luser is told 
+The wise sage luser is told about the Chat and uses it. The luser is told
 about the IRC and is looking for it. The flock are told about the Tao and
 make a fool of the IRC.
 
@@ -99,7 +99,7 @@ If there was no laughter, there would be no Tao.
 The master says:
 "Without the Tao of Internet Relay Chat, life becomes meaningless."
 
-The Relay of the old time was mysterious and sacred. We can neither imagine 
+The Relay of the old time was mysterious and sacred. We can neither imagine
 its thoughts nor path; we are left but to describe.
 
 
@@ -113,7 +113,7 @@ he exclaimed:
 	"I don't know whether I am Wumpus dreaming that I am a client,
 	 or a client dreaming that I am Wumpus!"
 
-So was the first Automata born. 
+So was the first Automata born.
 
 The master Nap then said:
 	"Any automata should not speak unless spoken to.
@@ -121,16 +121,16 @@ The master Nap then said:
 
 Thus replied the master Gnarfer:
 	"The lusers shall keep in mind that a automata can be either good or
-	 bad. Create good automata, and the IRC will hail you and you will 
-	 gain fame and fortune. Create bad automata and people will start to 
+	 bad. Create good automata, and the IRC will hail you and you will
+	 gain fame and fortune. Create bad automata and people will start to
 	 hate you, and finaly you will be /KILLed to ethernal damnation"
 
-Many lusers have fallen into the clutches of ethernal damnation. They where 
+Many lusers have fallen into the clutches of ethernal damnation. They where
 not following the Tao.
 
 
 -----
-There once was a luser who went to #BotSex. Each day he saw the automatons. 
+There once was a luser who went to #BotSex. Each day he saw the automatons.
 The luser decided that he also would have such a automata.
 He asked another luser for his automata. The other luser gave his automata
 away.
@@ -152,8 +152,8 @@ You must must BE the IRC before automating."
 
 
 -----
-Master BigCheese gave birth to master Troy; his duty clear. Master Troy gave 
-birth to master Phone, for the Tao of Irc must be eternal and must flow as the 
+Master BigCheese gave birth to master Troy; his duty clear. Master Troy gave
+birth to master Phone, for the Tao of Irc must be eternal and must flow as the
 ceaseless river of Time itself.
 
 
@@ -161,16 +161,16 @@ ceaseless river of Time itself.
 Master Phone once said about the ircII client:
 	"public_msg is for a message from someone NOT on the channel
 	 public_other is for a message on a channel that doesn't belong to
-	 a window. public is for a message on a channel that belongs to a 
+	 a window. public is for a message on a channel that belongs to a
 	 window!"
 
 Out of this raised the mighty chaos.
 
 
 -----
-The sage luser came to the master who wrote automata without the help of 
-master Phone. The sage luser asked the master who wrote automata: "Which is 
-easiest to make. A automata with the help of master Phone or an automata 
+The sage luser came to the master who wrote automata without the help of
+master Phone. The sage luser asked the master who wrote automata: "Which is
+easiest to make. A automata with the help of master Phone or an automata
 made with the help of a language ?"
 
 The master who wrote automata then replied:
@@ -196,13 +196,13 @@ This is the essence of Tao of IRC automatas.
 A client should be light and be used for communication. The spirit of a good
 client is that it should be very convinient for the luser to use, but hard
 for the luser who want to create automata.
-There should never ever be too many functions or too few functions. 
+There should never ever be too many functions or too few functions.
 
 There should always be a ignore.
 
 Without ignore the client is not within the Tao of Chating.
 
-The client should always respond the luser with messages that will not 
+The client should always respond the luser with messages that will not
 astnonish him too much. The server likewise. If the server does not, then it
 is the clients job to explain what the server says.
 
@@ -220,7 +220,7 @@ the Protocol.
 should it always work ? Only a fool would expect such. But, clients are made
 by humans, and humans are not perfect. Only Tao is.
 
-The IRC is solid. The IRC is floating, and will always be dynamic. Live with 
+The IRC is solid. The IRC is floating, and will always be dynamic. Live with
 that or /quit."
 
 
@@ -232,13 +232,13 @@ regardless of how the client connects to the server.
 
 "Is the Tao in irc ?" asked the luser.
 "It so is" replied the masters of #IrcHelp.
-"Is the Tao in the ircII, Kiwi, rxirc, vms, rockers and msa ?" asked the 
+"Is the Tao in the ircII, Kiwi, rxirc, vms, rockers and msa ?" asked the
 luser.
-"In all of them and in the TPC, irchat, zenirc, zircon X11-irc and even the 
+"In all of them and in the TPC, irchat, zenirc, zircon X11-irc and even the
 dos irc has the Tao" said the master quietly.
-"Is the Tao in a telnet connection directly to the server ?" 
+"Is the Tao in a telnet connection directly to the server ?"
 
-The master then was quiet for a long time and said. "Please leave, such 
+The master then was quiet for a long time and said. "Please leave, such
 questions are not within the Tao of IRC".
 
 
@@ -248,9 +248,9 @@ The master says: "Without the Protocol of TCP the messages will not travel.
 
 
 -----
-There once was a luser who used the ircII client. "ircII can do anything I 
-ever need for using IRC" said the emacs client user, "I have /ON's, I have 
-assignments, I have aliasing. Why don't you use this instead of the huge 
+There once was a luser who used the ircII client. "ircII can do anything I
+ever need for using IRC" said the emacs client user, "I have /ON's, I have
+assignments, I have aliasing. Why don't you use this instead of the huge
 emacs client, which also has a messy screen?"
 The emacs client user then replied by saying that "it is better to have a
 scripting language that is the client instead of have a client that has
@@ -259,14 +259,14 @@ a scripting language." Upon hearing this, the ircII client luser fell silent.
 
 -----
 The master Wumpus said: "Time for you to leave. I did, now I'm happy."
-The master Gnarfer replied: "Use, but never overuse IRC, then you will also 
+The master Gnarfer replied: "Use, but never overuse IRC, then you will also
 be happy within IRC"
 
 
 -----
-A luser came unto the masters of #EU-Opers and asked, "How can I be, yet not 
+A luser came unto the masters of #EU-Opers and asked, "How can I be, yet not
 be, a user@host within the IRC?"
 The masters of #EU-Opers replied: "To be Tao is to be ones true self. To hide
-ones self is not Tao, and is not IRC, you have much to learn before you shall 
+ones self is not Tao, and is not IRC, you have much to learn before you shall
 be at rest within the Flow of Irc.  Please leave"
 
diff --git a/doc/challenge.txt b/doc/challenge.txt
index 48e767a..790b588 100644
--- a/doc/challenge.txt
+++ b/doc/challenge.txt
@@ -61,7 +61,7 @@
 
        openssl genrsa -des3(1) -out rsa.key 1024(2)
        openssl rsa -in rsa.key -pubout -out rsa.pub
-   
+
 
    (1)
            The -des3 must be included in order to create a key with a
diff --git a/doc/kline.txt b/doc/kline.txt
index 6c72310..b82c5a2 100644
--- a/doc/kline.txt
+++ b/doc/kline.txt
@@ -1,6 +1,6 @@
 /* doc/kline.txt - Overview of the remote kline system
- * 
- * Copyright (C) 2005-2012 Hybrid Development Team
+ *
+ * Copyright (C) 2005-2013 Hybrid Development Team
  *
  * $Id$
  */
@@ -61,8 +61,8 @@ block in ircd.conf.
 The shared block contains two settings, a user@host mask of the oper
 who is allowed to K-Line, and a servername.
 
-- If both of these options are present, K-Lines will only be allowed 
-  from that specific user@host on that specific server. 
+- If both of these options are present, K-Lines will only be allowed
+  from that specific user@host on that specific server.
 - If only the servername is present, all K-Lines from opers on that
   server will be accepted.
 - If only the user@host is present, all K-Lines from that user@host on
@@ -70,11 +70,11 @@ who is allowed to K-Line, and a servername.
 - If neither are present, the shared block is invalid.
 
 shared {
-	/* The name of the server we allow K-Lines from */
-	name = "this.server.net";
+        /* The name of the server we allow K-Lines from */
+        name = "this.server.net";
 
-	/* the user@host allowed to K-Line */
-	user = "user@host.com";
+        /* the user@host allowed to K-Line */
+        user = "user@host.com";
 };
 
 Server to Server Protocol
@@ -87,15 +87,15 @@ without a KLN capability.
 Server to server messages are formatted like this:
 
   ":oper KLINE target.server duration user host :reason"
-    
+
 Note the difference between hybrid-6 GLINE which explicitly passed
 the oper user@host and server along. This was originally done to handle
-possible desync conditions, but is now shelved in favor of saving 
+possible desync conditions, but is now shelved in favor of saving
 some bandwidth.
 
-oper:		the nick of the oper performing the K-Line
-target.server:	the server(s) this K-Line is destined for
-duration:	the duration if a TK-Line, 0 if permanent.
-user:		the 'user' portion of the K-Line
-host:		the 'host' portion of the K-Line
-reason:		the reason for the K-Line.
+oper:           the nick of the oper performing the K-Line
+target.server:  the server(s) this K-Line is destined for
+duration:       the duration if a TK-Line, 0 if permanent.
+user:           the 'user' portion of the K-Line
+host:           the 'host' portion of the K-Line
+reason:         the reason for the K-Line.
diff --git a/doc/modeg.txt b/doc/modeg.txt
index f3b91dc..f7b5575 100644
--- a/doc/modeg.txt
+++ b/doc/modeg.txt
@@ -1,7 +1,7 @@
                          User Mode +g Documentation
 
 Hybrid 7 includes a new and power feature that all users can take advantage
-of to help prevent flooding and unwanted messages.  This new feature is 
+of to help prevent flooding and unwanted messages.  This new feature is
 invoked by setting user mode +g.  When a client is set +g, that user will
 be in "Caller ID" mode.  Any user that messages a +g client will receive
 a numeric saying that they are in +g (server side ignore) mode.  The target
@@ -50,7 +50,7 @@ changed their nick.
 
 Viewing the accept list is also very easy.  Issue the raw command ACCEPT *.
 Removing a user from your accept list is also simple.  Issue the command
-ACCEPT -<nick>.  
+ACCEPT -<nick>.
 
                               Sample Session
 
@@ -118,15 +118,15 @@ Hwy-LL will now only accept messages from Hwy101 and services.
 --
 
 The nicks to be added can be in ANY order, however you cannot add or remove
-AND list.  
+AND list.
     /ACCEPT x,y,-z,f,-a would be acceptable.
     /ACCEPT x,y,-z,* would ignore the * and generate an invalid nick
                      response.
 
 Like Dalnet and Undernet's SILENCE system, the accept list only exists while
 you are connected to IRC.  In order for you to have the same accept list
-every time you come onto IRC, you must put the accept commands into your 
-client's auto-perform, or manually issue the commands each time.  
+every time you come onto IRC, you must put the accept commands into your
+client's auto-perform, or manually issue the commands each time.
 
 This system may seem similar to the SILENCE system, but it is actually a
 reverse SILENCE.  SILENCE ignores certain users and allows the rest.  Mode
diff --git a/doc/modes.txt b/doc/modes.txt
index 7b0f053..4b1f52b 100644
--- a/doc/modes.txt
+++ b/doc/modes.txt
@@ -1,5 +1,5 @@
                         User and Channel Modes Guide
-			----------------------------
+                        ----------------------------
 
 In /VERSION one might see something like this:
 
@@ -64,12 +64,12 @@ Channel Modes:
                     set at the same time as +s.
 +r - registered   - Channel has been registered
 +R - regonly      - Only registered clients may join a channel with that mode set
-+s - secret       - The channel does not show up on NAMES or LIST or in the 
++s - secret       - The channel does not show up on NAMES or LIST or in the
                     WHOIS channel list unless you are a member of the channel
 +S - sslonly      - This mode will prevent anyone who isn't securely connected
                     via SSL/TLS from joining the channel.
 +t - topic        - Only chanops can change the topic
-+v - voice        - Can speak in a moderated channel, and is exempt from flood 
++v - voice        - Can speak in a moderated channel, and is exempt from flood
                     restrictions
 
 The third part of the 004 numeric lists channel modes that require arguments.
diff --git a/doc/resv.txt b/doc/resv.txt
index d1e0fdc..8bcd135 100644
--- a/doc/resv.txt
+++ b/doc/resv.txt
@@ -1,5 +1,5 @@
 /*
- * doc/resv.txt - Overview of the resv system 
+ * doc/resv.txt - Overview of the resv system
  * Lee Hardy <lee@leeh.co.uk>
  *
  * Copyright (C) 2001 Hybrid Development Team
@@ -64,7 +64,7 @@
   then a /rehash, should do the trick.
 
   If the resv was made using /RESV, then use the unresv command:
-    
+
     Syntax: /quote unresv <#channel|nick>
 
 - Can I make a resv on all servers?
@@ -102,7 +102,7 @@
 
   Yes. It takes the same format as creating a resv on a normal channel:
     /resv &clones :no clonebots!
-    
+
 - Do you support wildcard channel resv's?
 
   No.  This is mainly for speed reasons.  When we are searching nicks, we
diff --git a/doc/serverhide.txt b/doc/serverhide.txt
index 49f575e..a2d4f67 100644
--- a/doc/serverhide.txt
+++ b/doc/serverhide.txt
@@ -41,7 +41,7 @@
        | Flattened LINKS is needed for any network that uses the hidden hub |
        | option. See below for more details.                                |
        +--------------------------------------------------------------------+
-        
+
      * Hidden server option: This option will hide the server from a
        flattened LINKS list on other servers. Opers will of course see the
        true routing of the network.