v2.2-ossxp-2

new patch: t/adc-enhanced.

topgit v1.5.5-ossxp

(really big config) 2 new rc variables

...to prevent auto-creation of repos from config, and to prevent
processing of ssh keys.  Also doc update

log message changes (warning: minor backward compat breakage)

The log message format has changed.  All log messages now have a common
prefix (timestamp, user, IP).  This is followed by $SSH_ORIGINAL_COMMAND
(or, in one special case, the name of the user's login shell).  Any
further text appears after this (currently this only happens in the case
of a successful push -- one for each ref pushed successfully)

add a new test to make sure "info" and "expand" show the right output

compile: kill spurious "user ... not in config" warnings

this happens when users are given rights to a repo via a groupname, and
GL_BIG_CONFIG is in effect

(important upgrade info here)

There has been a format change to the compiled output file.  As the
CHANGELOG says:

    Upgrading to v1.5 from any version prior to v1.5 requires an extra
    step for people who installed gitolite using the "system install /
    user setup" method described in doc/0-INSTALL.mkd.  For such
    installations, after the administrator has upgraded gitolite
    system-wide, each "gitolite host" user must run `gl-setup` once
    (without any arguments).

    This is *not* an issue if you installed using src/gl-easy-install.

the most common problems an admin will see

an admin who refuses to read messages that show up on the screen, that is ;-)

(security) a different fix in place of 5fd9328

SECURITY NOTE: if you deleted or renamed a pubkey file after 5fd9328
went in (April 12th), please:

  - upgrade asap, then
  - go to your latest gitolite-admin clone and "git push -f"

Otherwise this is not urgent.

5fd9328 (and its minor successor 813a2a9) were about preventing the
gitolite admin from sneaking in files to src/ and hooks/ into
$GL_ADMINDIR.  It seemed easy enough to do this by converting the
path-less checkout to a with-paths checkout, but this has caused a worse
problem -- deleting a keydir/foo.pub now no longer has an effect; the
file still hangs around in the work tree.

Ouch!  (and thanks to teukka for noticing)

We now do this check as a separate step, so the checkout can revert to
being path-less.