dragonmtn-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Dragonmtn-commits] Changes to snowwhiteHelp/chanserv/log.xml


From: Mark Loeser
Subject: [Dragonmtn-commits] Changes to snowwhiteHelp/chanserv/log.xml
Date: Sat, 20 Aug 2005 02:34:58 -0400

Index: snowwhiteHelp/chanserv/log.xml
diff -u snowwhiteHelp/chanserv/log.xml:1.1 snowwhiteHelp/chanserv/log.xml:1.2
--- snowwhiteHelp/chanserv/log.xml:1.1  Mon Apr 11 10:10:55 2005
+++ snowwhiteHelp/chanserv/log.xml      Sat Aug 20 06:34:42 2005
@@ -1,29 +1,26 @@
 <help service="chanserv">
- <topic name="LOG">
-  <command name="LOG">
-   <syntax>
-     /ChanServ LOG #&lt;message&gt;
-   </syntax>
-
-   <desc>
-     This command allows an operator to write a message to services logs to
-     annotate other logged commands.
-   </desc>
-   
-   <section>
-     It should be used when a command is used in an unusual way, or when an
-     oper is likely to need information about a channel's situation in handling
-     future requests.
-   </section>
-
-   <examples>
-     <ex pre="To log closing #BadChannel due to services abuse:">
-       /ChanServ log #BadChannel was closed due to services abuse
-     </ex>
-     <ex pre="To log deleting #BadChannel on founder request:">
-       /ChanServ LOG #BadChannel deleted by founder request, not abuse
-     </ex>
-   </examples>
-  </command>
- </topic>
-</help>
\ No newline at end of file
+       <topic name="LOG">
+               <command name="LOG">
+                       <syntax>
+                               /ChanServ LOG #&lt;message&gt;
+                       </syntax>
+                       <desc>
+                               This command allows an operator to write a 
message to services logs to
+                               annotate other logged commands.
+                       </desc>
+                       <section>
+                               It should be used when a command is used in an 
unusual way, or when an
+                               oper is likely to need information about a 
channel's situation in 
+                               handling future requests.
+                       </section>
+                       <examples>
+                               <ex pre="To log closing #BadChannel due to 
services abuse:">
+                                       /ChanServ log #BadChannel was closed 
due to services abuse
+                               </ex>
+                               <ex pre="To log deleting #BadChannel on founder 
request:">
+                                       /ChanServ LOG #BadChannel deleted by 
founder request, not abuse
+                               </ex>
+                       </examples>
+               </command>
+       </topic>
+</help>




reply via email to

[Prev in Thread] Current Thread [Next in Thread]