about summary refs log tree commit diff
diff options
context:
space:
mode:
authorAlexander Barton <alex@barton.de>2013-08-02 02:16:21 +0200
committerAlexander Barton <alex@barton.de>2013-08-02 02:16:21 +0200
commit24183b1a918d7475f9fac28a10c6ae49c93e24b3 (patch)
tree45e7ce7344039d1d84e1b7076a1447281984ff9e
parent888c52468373e3680fa1138830643848675779e5 (diff)
downloadngircd-24183b1a918d7475f9fac28a10c6ae49c93e24b3.tar.gz
ngircd-24183b1a918d7475f9fac28a10c6ae49c93e24b3.zip
Commands.txt: Fix <target> description of TRACE command
-rw-r--r--doc/Commands.txt6
1 files changed, 5 insertions, 1 deletions
diff --git a/doc/Commands.txt b/doc/Commands.txt
index 72e2eda5..49a84f65 100644
--- a/doc/Commands.txt
+++ b/doc/Commands.txt
@@ -479,12 +479,16 @@ Status and Informational Commands
 	 - RFC 2812, 3.4.6 "Time message"
 
 - TRACE
-	TRACE [<server>]
+	TRACE [<target>]
 	.
 	Find the route to a specific server and send information about its
 	peers. Each server that processes this command reports back to the
 	sender about it: the replies from pass-through servers form a chain
 	which shows the route to the destination.
+	.
+	<target> can be a server name, the nickname of a client connected to
+	a specific server, or a mask matching a server name in the network.
+	The server of the current connection is used when <target> is omitted.
 
 	References:
 	 - RFC 2812, 3.4.8 "Trace message"