# 
# patch "monotone.texi"
#  from [abb58b17ca2cd128b1fc61e4b2c17e810008980b]
#    to [400563b74b0f270eace44e51338cbe6b368606a8]
# 
========================================================================
--- monotone.texi	abb58b17ca2cd128b1fc61e4b2c17e810008980b
+++ monotone.texi	400563b74b0f270eace44e51338cbe6b368606a8
@@ -6030,8 +6030,16 @@
 key fingerprints of each key in your database, as key ID strings are
 ``convenience names'', not security tokens.
 
+Note also that, unlike the equivalent read permission hook, the write
+permission hook does not take a @var{branch} name as an argument.  There
+is presently no way to selectively grant write access to different
+branches via netsync, for a number of reasons. Contributions in the
+database from different authors can be selectively trusted using the
address@hidden Evaluation Hooks} instead.
+
 @end ftable
 
address@hidden Evaluation Hooks}
 @subsection Trust Evaluation Hooks
 
 Monotone makes heavy use of certs to provide descriptive information