deac/gitolite
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity

Fixes documentation typos

Browse source
This commit is contained in:
Chris Tilden 2011-08-24 13:12:42 -07:00
parent e5e95794ef
commit 0172868da7
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
doc/gitolite-and-ssh.mkd
View file

@ -135,7 +135,7 @@ When `gl-auth-command` gets control, it looks at the first argument
`SSH_ORIGINAL_COMMAND` variable to find out which repository you want to
access, and whether you're reading or writing.
Now is has user, repository, and access requested (read/write), gitolite looks
Now that it has a user, repository, and access requested (read/write), gitolite looks
at its config file, and either allows or rejects the request.
But this cannot differentiate between different branches within a repo; that
@ -155,7 +155,7 @@ happen -- see `git help hooks` for details. One of those hooks is the
tag is about to be updated. The hook is passed the name of the branch or tag,
the old SHA1 value, and the new SHA1 value, as arguments. Hooks that are
called *before* an action happens are allowed to prevent that action from
happening y returning an error code.
happening by returning an error code.
When gitolite is told to create a new repository (by the admin), it installs
a special update hook. This hook takes all the information presented, looks