equal
deleted
inserted
replaced
298 </listitem> |
298 </listitem> |
299 <listitem> |
299 <listitem> |
300 Whether to allow any access to a repository |
300 Whether to allow any access to a repository |
301 </listitem> |
301 </listitem> |
302 <listitem> |
302 <listitem> |
303 Whether to allow a changeset, which is on a some branch |
303 Whether to allow a changeset |
304 </listitem> |
|
305 <listitem> |
|
306 Whether to allow a changeset which changes a particular file |
|
307 </listitem> |
304 </listitem> |
308 </itemizedlist> |
305 </itemizedlist> |
309 <para> |
306 <para> |
310 When the first two of these decisions are being made, nothing is known |
307 When the first two of these decisions are being made, nothing is known |
311 about what files might be changed, and so all file and branch conditions |
308 about any changsets that might be pushed, and so all file and branch |
312 automatically succeed for the purpose of such decisions. This means that |
309 conditions automatically succeed for the purpose of such decisions. For the |
313 doing tricky things with file conditions can have counterintuitive |
310 third condition, every file changed in the changeset must be allowed by a |
314 consequences: |
311 <literal>write</literal> or <literal>init</literal> rule for the changeset |
|
312 to be allowed. |
|
313 </para> |
|
314 <para> |
|
315 This means that doing tricky things with file conditions can have |
|
316 counterintuitive consequences: |
315 </para> |
317 </para> |
316 <itemizedlist> |
318 <itemizedlist> |
317 <listitem> |
319 <listitem> |
318 <para>You cannot limit read access to a subset of a repository with a "read" |
320 <para>You cannot limit read access to a subset of a repository with a "read" |
319 rule and a file condition: any user who has access to a repository can read |
321 rule and a file condition: any user who has access to a repository can read |