allow simple macros in conf file
(minor) fixes to lint program, mainly usage message
'gitolite mirror' needs to set exit code on push failure
minor fixups to some non-core programs

(following a bit of a doc shakeup)
sudo command: CLI fix: 2 non-empty args required
new features relating to creating wild repos:

  - new 'create' command for explicit creation
  - new 'AutoCreate' trigger to prevent auto-creation on read operations
    or both read and write operations
  - a few related fixups to the perms command
Fixed bug in lock script

the unlock command was not checking the correct hash key to match
the user name
oops; hashes were getting printed twice in certain cases...

harmless but wasteful
prevent empty %groups being created in compiled conf

this would happen if @all was used but no actual groups were defined,
and would in turn cause a parse error on the compiled conf because it
now ends with a 'false'.

thanks to Jelle Raaijmakers
a few minor changes

  * minor typos
  * perltidy on Tsh
  * a minor optimisation to "do" in gl-conf
  * remove inapplicable caveat in fork command
bugfix: don't delete description file when running perms

thanks to drue on #gitolite for catching it
(minor) lint had syntax errors

thanks to xcat on #gitolite for catching it
(shows you how often it gets used I guess!)
Set Content-Type to text/plain for gitolite commands over http

Explicitly set "Content-Type: text/plain" for gitolite commands when
issued over http, so that it is possible to see the output with normal
browsers.

(At least) Apache httpd might set the Content-Type to something
different and triggers a download instead of showing the text directly.

Signed-off-by: Sven Strickroth <email@cs-ware.de>
new trigger: update-gitweb-daemon-from-options

another way to update gitweb and daemon access lists
(minor) macro buglets

  - allow parameter-less macros
  - allow macro body to start on next line
add more detail to error message

this error normally happens due to some permission issue on the log
file, but we weren't printing the actual cause, so it was confusing
CREATOR need only be a "word" in wild repo patterns

this was a v2 compat breakage, caught by Dominik Schäfer
(schaedpq at gmail)
fix bug in list-dangling-repos

Still, I would advise caution if you use this as a basis for deleting
repos from the file system.  A bug in this program could cause you to
lose important data!
D: allow rm and unlock to be disabled
minor bugly...

please remember we make up words here, like refex was a word we created
to mean "a regex that matches a ref".

A "bugly", then, is a bug that's merely ugly (and not a real problem!)