#
#
# patch "monotone.texi"
#  from [7ca3e47a431d45e0b4053dac7507569bf55ab628]
#    to [3d1dbfaa53dc2db48427325a0164d27637d7a712]
#
============================================================
--- monotone.texi	7ca3e47a431d45e0b4053dac7507569bf55ab628
+++ monotone.texi	3d1dbfaa53dc2db48427325a0164d27637d7a712
@@ -4692,14 +4692,15 @@ @section Tree
 @emph{must} provide a @var{branchname}; monotone will attempt to infer
 @var{id} as the unique head of @var{branchname} if it exists.
 
address@hidden mtn clone address@hidden @var{address} @var{directory}
address@hidden mtn clone @var{address}[:@var{port}] @var{branchname} address@hidden
 
 The clone command is a helper command that performs the roles of a
 number of other commands all at once.  Firstly, it constructs a new
 database.  It then populates this database by @command{pull}ing any data
 in the branch @var{branchname} from the remote database, @var{address}.
 Finally, it copies the files out of the newly created database into a
-local directory, just as @command{checkout} would.  The created
+local directory, just as @command{checkout} would.  If no @var{directory}
+is given, the @var{branchname} is used as directory.  The created
 database is placed in the new workspace as @address@hidden/_MTN/mtn.db}.
 
 @item mtn disapprove @var{id}