df157e72b5
This patch is dedicated to the person who, when referred to [1] for gitweb access help, assumed we're talking about a Unix userid called "gitweb" and said it still doesn't work. He looked at the description examples and wasn't sure what to do with them. Finally, he missed the sentence "All gitolite does is:" in the document, and assumed *he* was supposed to do what the next 3 bullets said (in this case, create the "description" file manually). He didn't once think of the gitolite.conf file as being the location for these instructions, or that "give read access" means "R = ..." instead of a Unix level "chmod ...". Do things have to be spelled out so goddamn clearly? Can't people think for a few seconds and see if there is another way before giving up? I blame the prevalence of Windows and GUI IDEs. People can only "click". They can't "think" anymore... [1]: http://sitaramc.github.com/gitolite/doc/2-admin.html#gwd |
||
---|---|---|
.. | ||
1-INSTALL.mkd | ||
2-admin.mkd | ||
3-faq-tips-etc.mkd | ||
admin-defined-commands.mkd | ||
big-config.mkd | ||
CHANGELOG | ||
COPYING | ||
delegation.mkd | ||
developer-notes.mkd | ||
gitolite-and-ssh.mkd | ||
gitolite.conf.mkd | ||
gitolite.rc.mkd | ||
hook-propagation.mkd | ||
http-backend.mkd | ||
install-transcript.mkd | ||
migrate.mkd | ||
mirroring.mkd | ||
mob-branches.mkd | ||
monkeysphere.mkd | ||
overkill.mkd | ||
packaging.mkd | ||
progit-article.mkd | ||
report-output.mkd | ||
shell-games.mkd | ||
ssh-troubleshooting.mkd | ||
uninstall.mkd | ||
who-uses-it.mkd | ||
wildcard-repositories.mkd |