#
#
# patch "monotone.texi"
#  from [1110f1b77c6209d8f6492adfa27df3197f6916b0]
#    to [7d7051f6053cc36046d27f8d43917840b589b3ca]
#
============================================================
--- monotone.texi	1110f1b77c6209d8f6492adfa27df3197f6916b0
+++ monotone.texi	7d7051f6053cc36046d27f8d43917840b589b3ca
@@ -2664,11 +2664,13 @@ @section Other Transports
 In the case of File URIs, @command{mtn} is run locally, so must be
 in your command execution path.
 
-In both cases, the database specified in the URI needs to exist
-already, and will be locked for the duration of the synchronization
-operation. Also note that monotone's default transport authentication
-is @emph{disabled} over these transports, to reduce the complexity of
-configuration and eliminate redundant protocol cost.
+In both cases, the database specified in the URI needs to exist already,
+and will be locked for the duration of the synchronization
+operation. Therefore, it must also be writable, even when monotone isn't
+going to modify it, as it is the case for @command{pull}.  Also note
+that monotone's default transport authentication is @emph{disabled} over
+these transports, to reduce the complexity of configuration and
+eliminate redundant protocol cost.
 
 Additional URI schemes can be supported by customization of the Lua
 hooks @code{get_netsync_connect_command} and