opendev/gerrit
Code Issues Proposed changes

Fix spelling errors in access-control.txt

Browse Source 
Change-Id: I303ce6c898f6107b1b1d59756917bf474d9b7252
This commit is contained in:
Gustaf Lundh
2013-05-08 15:05:12 +01:00
committed by David Pursehouse
parent 94d00838d4
commit a28a1d2b1c
1 changed files with 8 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
Documentation/access-control.txt
View File

@@ -53,7 +53,7 @@ Non-Interactive Users
~~~~~~~~~~~~~~~~~~~~~
This is an internal user group, members of this group are not expected
to perform interactive operations on the Gerrit web frontend.
to perform interactive operations on the Gerrit web front-end.
However, sometimes such a user may need a separate thread pool in
order to prevent it from grabbing threads from the interactive users.
@@ -500,7 +500,7 @@ Push Merge Commits
~~~~~~~~~~~~~~~~~~~~
The `Push Merge Commit` access right permits the user to upload merge
commits. It's an addon to the <<category_push,Push>> access right, and
commits. It's an add-on to the <<category_push,Push>> access right, and
so it won't be sufficient with only `Push Merge Commit` granted for a
push to happen. Some projects wish to restrict merges to being created
by Gerrit. By granting `Push` without `Push Merge Commit`, the only
@@ -767,7 +767,7 @@ Optional access rights to grant:
CI system
~~~~~~~~~
A typical Continous Integration system should be able to download new changes
A typical Continuous Integration system should be able to download new changes
to build and then leave a verdict somehow.
As an example, the popular
@@ -840,7 +840,7 @@ power in the form of being able to delete branches. Optionally these users
also have the power to configure access rights in gits assigned to them.
[WARNING]
These users should be really knowledgable about git, for instance knowing why
These users should be really knowledgeable about git, for instance knowing why
tags never should be removed from a server. This role is granted potentially
destructive access rights and cleaning up after such a mishap could be time
consuming!
@@ -985,8 +985,8 @@ category. In the "`All-Projects`" we define the following rules:
====
[access "refs/heads/stable*"]
label-Release-Proces = block -1..+1 group Anonymous Users
label-Release-Proces = -1..+1 group Release Engineers
label-Release-Process = block -1..+1 group Anonymous Users
label-Release-Process = -1..+1 group Release Engineers
====
[[conversion_table]]
@@ -1020,7 +1020,7 @@ Conversion table from 2.1.x series to 2.2.x series
In Gerrit 2.2.x, the way to set permissions for upload has changed entirely.
To upload a change for review is no longer a separate permission type,
instead you grant ordinary push permissions to the actual
recieving reference. In practice this means that you set push permissions
receiving reference. In practice this means that you set push permissions
on `refs/for/refs/heads/<branch>` rather than permissions to upload changes
on `refs/heads/<branch>`.
@@ -1113,7 +1113,7 @@ Kill Task
Allow the operation of the link:cmd-kill.html[kill command over ssh]. The
kill command ends tasks that currently occupy the Gerrit server, usually
a replication task or a user initiated task such as an upload-pack or
recieve-pack.
receive-pack.
[[capability_priority]]