# HG changeset patch
# User Paul Crowley <paul@lshift.net>
# Date 1255539815 -3600
# Node ID b7e78f9705e6f1b4fc6fd79f35eaeb1d7dd5c33c
# Parent  44ee9dc3bba96aad84486535ff070196c09f8cea
There are only three decisions, honest

diff -r 44ee9dc3bba9 -r b7e78f9705e6 doc/manual.docbook
--- a/doc/manual.docbook	Wed Oct 14 17:45:30 2009 +0100
+++ b/doc/manual.docbook	Wed Oct 14 18:03:35 2009 +0100
@@ -300,18 +300,20 @@
 Whether to allow any access to a repository
 </listitem>
 <listitem>
-Whether to allow a changeset, which is on a some branch
-</listitem>
-<listitem>
-Whether to allow a changeset which changes a particular file
+Whether to allow a changeset
 </listitem>
 </itemizedlist>
 <para>
 When the first two of these decisions are being made, nothing is known
-about what files might be changed, and so all file and branch conditions
-automatically succeed for the purpose of such decisions. This means that
-doing tricky things with file conditions can have counterintuitive
-consequences:
+about any changsets that might be pushed, and so all file and branch
+conditions automatically succeed for the purpose of such decisions. For the
+third condition, every file changed in the changeset must be allowed by a
+<literal>write</literal> or <literal>init</literal> rule for the changeset
+to be allowed.
+</para>
+<para>
+This means that doing tricky things with file conditions can have
+counterintuitive consequences:
 </para>
 <itemizedlist>
 <listitem>