#
#
# patch "monotone.texi"
#  from [f36f9ea6bc0159051867e484d01421952f71f9ef]
#    to [d428161e6f07931dba1dbef90481d39015416620]
#
============================================================
--- monotone.texi	f36f9ea6bc0159051867e484d01421952f71f9ef
+++ monotone.texi	d428161e6f07931dba1dbef90481d39015416620
@@ -5165,6 +5165,39 @@ @section Key and Cert Trust
 Monotone would trust a cert on that revision with that value signed by
 those keys.
 
address@hidden mtn ssh_agent_add
+
+This command will add your monotone keys to your current ssh-agent session.
+You will be asked for the passphrase for each of your monotone private keys
+and they will be added to the ssh-agent. Once this is done you should be able
+to type @emph{ssh-add -l} and see your monotone key listed. When you
+subsequently use these keys through monotone it will use ssh-agent for signing
+without asking your for your passphrase.
+
+This command is mainly for use in a session script as monotone will automatically
+add your keys to ssh-agent on first use if it is available. For example the
+following two examples are equivalent:
+
address@hidden
address@hidden
+$ mtn ssh_agent_add
+enter passphrase for key ID address@hidden:
+$ mtn ci -m"Changed foo to bar"
+$ mtn push -k address@hidden
address@hidden group
address@hidden smallexample
+
address@hidden
address@hidden
+$ mtn ci -m"Changed foo to bar"
+enter passphrase for key ID address@hidden:
+$ mtn push -k address@hidden
address@hidden group
address@hidden smallexample
+
+In the second example, monotone automatically added the key to ssh-agent, making
+entering the passphrase not needed during the push.
+
 @item mtn ssh_agent_export @var{filename}
 
 This command will export your private key in a format that ssh-agent
@@ -5186,7 +5219,7 @@ @section Key and Cert Trust
 Enter passphrase for /home/user/.ssh/id_monotone:
 Identity added: /home/user/.ssh/id_monotone (/home/user/.ssh/id_monotone)
 $ mtn ci -m"Changed foo to bar"
-$ mtn push
+$ mtn push -k address@hidden
 @end group
 @end smallexample