Skip to content


Subversion checkout URL

You can clone with
Download ZIP
Browse files

(accumulated minor docfixes)

  • Loading branch information...
commit c5a65b9228ae14b4dce7d4027642063e81ddd540 1 parent 4e8c280
@sitaramc authored
3  emergencies.mkd
@@ -146,6 +146,9 @@ the answer, but here's a list of files you should blow away.
* having the home directory in a partition that is mounted noexec.
+ * having the default shell be something like /bin/false, and/or not having
+ the default shell be part of /etc/shells.
## #ngp things that are not gitolite problems
There are several things that appear to be gitolite problems but are not. I
5 g2migr.mkd
@@ -90,9 +90,10 @@ Some of them have links where there is more detail than I want to put here.
* `GIT_PATH` **dropped**, **requires presetting**.
- If you need its functionality, add these lines to the end of the rc file:
+ If you need this, manipulate the PATH environment variable directly. Just
+ put something like this at the end of the rc file:
- $ENV{PATH}="...whatever you want...";
+ $ENV{PATH} = "/some/non-standard/path:$ENV{PATH}";
### medium impact
4 git-config.mkd
@@ -37,7 +37,9 @@ examples). Other forms of the `git config` command (`--add`, the
> ----
-You can also use the special value `%GL_REPO` in the string to save typing:
+You can also use the special values `%GL_REPO` and `%GL_CREATOR` in the
+string. The former is available to all repos, while the latter is only
+available to [wild][] repos.
repo foo bar baz
config hooks.mailinglist = %GL_REPO-commits@example.tld
15 index.mkd
@@ -51,12 +51,19 @@ most people see:
## #contact contact
+**NOTE** Unless you have very good reasons, please use the mailing list below
+instead of mailing me personally. If you have to mail me, use the gmail
+address instead of my work address.
* author:,
- * general discussion list:
- * list subscribe address:
- * announcements and notices list:
- * list subscribe address:
+ * mailing list for questions and general discussion:
+ *
+ * subscribe address:
+ * mailing list for announcements and notices:
+ *
+ * subscribe address:
* IRC: #git and #gitolite on freenode. Note that I live in India (UTC+0530
time zone).
2  ips.mkd
@@ -29,7 +29,7 @@ a detailed log of every command you typed, and the complete response you got.
I do not ask for this information to help you -- that's only a front. I
*know* these instructions work (at least on any Linux that already has git
installed), so the real reason is to find where you mistyped something and
-mock you for that,
+mock you for that.
### Assumptions
2  master-toc.mkd
@@ -105,6 +105,7 @@
* ([link][partial-copy]: faking selective READ control)
* using pubkeys obtained [from elsewhere][keysonly]
* ([link][pushcode]: updating code via the admin repo)
+ * giving users [their own repos][gh]
## interfacing with [external][] tools
@@ -140,6 +141,7 @@
* commands
* trigger programs
* sugar
+ * (appendix 1) notes on the INPUT trigger
## [non-core][] programs shipped with gitolite
5 rules.mkd
@@ -34,6 +34,11 @@ There are also other, less commonly used, [types of permissions][write-types].
A refex is an expression that matches the ref (i.e., branch or tag) being
pushed. See [this][refex] for more info.
+You can also use [virtual refs][vref] to perform extra checks and controls
+that you can't do with just the normal ref (like refs/heads/master) being
+pushed. The most common example is restricting pushes by dir/file name, but
+there are lots of other possibilities.
### when are the rules checked?
There are 2 places where access rules are checked.

0 comments on commit c5a65b9

Please sign in to comment.
Something went wrong with that request. Please try again.