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

(minor) doc fixes

Browse source
This commit is contained in:
Sitaram Chamarty 2010-11-05 16:04:58 +05:30
parent 9716e32456
commit 70359ce9ba
3 changed files with 19 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
conf/example.gitolite.rc
View file

@ -8,7 +8,7 @@
# self-explanatory and easy to maintain perl syntax :-)
# --------------------------------------
# Do not uncomment these values unless you know what you're doing
# Do not change the next two lines unless you know what you're doing
# $GL_PACKAGE_CONF = "";
# $GL_PACKAGE_HOOKS = "";

10
doc/ssh-troubleshooting.mkd
View file

@ -277,7 +277,14 @@ Otherwise, run these checks:
If it prints the gitolite version and access info (see
[doc/report-output.mkd][repout]), you managed to overwrite the `id_rsa`
keypair with the `sitaram` keypair, or something equally weird.
keypair with the `sitaram` keypair, or something equally weird. This is
because a gitolite key, when used without any actual command, defaults to
running gitolite's internal "info" command.
**NOTE** starting with [version 5.6][openssh56], openssh will "Kill
channel when pty allocation requests fail". This means that, instead of
seeing the version and access info as described above, you may only get a
message about pty allocation failure, followed by "connection closed".
2. `ssh gitolite info` should print some gitolite version and access info.
If you get the output of the GNU info command instead, you probably reused
@ -466,3 +473,4 @@ bigger problems than gitolite install not working!)]
[urls]: http://github.com/sitaramc/gitolite/blob/pu/doc/1-INSTALL.mkd#URLs_for_gitolite_managed_repos
[repout]: http://github.com/sitaramc/gitolite/blob/pu/doc/report-output.mkd
[transcript]: http://github.com/sitaramc/gitolite/blob/pu/doc/install-transcript.mkd
[openssh56]: http://www.openssh.org/txt/release-5.6

9
doc/wildcard-repositories.mkd
View file

@ -122,6 +122,15 @@ users are "READERS" and which are "WRITERS". See later for details.
<a name="_side_note_line_anchored_regexes"></a>
### side-note: valid regexes
Due to projects like `gtk+`, the `+` character is now considered a valid
character for an *ordinary* repo. Therefore, a pattern like `foo/.+` does not
look like a regex to gitolite. Use `foo/..*` if you want that.
Also, `..*` by itself is not considered a valid repo pattern. Try
`[a-zA-Z0-9].*`.
### side-note: line-anchored regexes
A regex like