Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Commits on Jun 12, 2010
  1. finally, open up my secret test scripts...

    authored
    ...after getting rid of most of the hardcoding (though not all!)
  2. report_basic forgot how to display wildcards during big-config change

    authored
    in addition, due to "+" becoming a valid character in a normal reponame,
    (think gtk+, etc), the pattern
    
        repo dev/CREATOR/.+
    
    doesn't look like a wildcard repo anymore, so we add an extra check that
    if CREATOR is mentioned, it *is* a wildcard.
    
    This has been added *only* to the report_basic function; it doesn't
    really matter anywhere else.
Commits on Jun 2, 2010
  1. compile: kill spurious "user ... not in config" warnings

    authored
    this happens when users are given rights to a repo via a groupname, and
    GL_BIG_CONFIG is in effect
  2. now you can disallow creation of new refs if you like

    authored
    see doc/3 for details (look for "separating delete and rewind rights"
    
    ----
    
    and for gerrit, this is one more thing it can do that we can too ;-)
    
    [the original text was somewhat misleading.  We mean "prevent someone
    from creating a branch that they have permissions to push".  That is
    what is now possible, where it was not possible before.]
Commits on Jun 1, 2010
  1. remove a few needless bashisms...

    authored
    Note: "able" still needs bash but it's an easy fix if you need to use it
    on a bash-challenged machine and care enough
Commits on May 31, 2010
  1. (contrib) how to enable or disable push for maintenance

    authored
    ...for some or all repos
    
    (and a minor bug fix in the adc.common-functions file)
  2. include VERSION details when using gl-system-install from a clone

    authored
    It works fine when you're installing off of a tar file because the
    Makefile also generates a VERSION file, but when doing from a clone you
    still need to generate it.
    
    (plus minor fix to easy install, in the same area of code)
Commits on May 29, 2010
Commits on May 28, 2010
  1. @madduck

    gitweb: default GL_USER to gitweb if not provided by CGI

    madduck authored committed
    If CGI.pm does not have a user, this patch causes the gitweb
    authentication code to assume "gitweb". This allows one to specify ACLs
    specifically for gitweb, separately from the @all catch-all.
    
    To: Sitaram Chamarty <sitaramc@gmail.com>
    Cc: Teemu Matilainen <teemu.matilainen@iki.fi>
    Signed-off-by: martin f. krafft <madduck@madduck.net>
Commits on May 23, 2010
  1. Merge branch 'add_host_nickname' into pu

    authored
    Conflicts:
    	src/gl-easy-install
  2. (minor fixups)

    authored
  3. @thectrain
Commits on May 21, 2010
  1. *major* doc revamp

    authored
    people will NOT read documentation, especially the bloody install
    documentation.  I'm about ready to throw in the towel and declare
    gitolite unsupported, take-it-or-leave-it.
    
    But I'm making one last attempt to refocus the install doc to better
    suit the "I know I'm very smart and I dont have to read docs so it's
    clearly your fault that I am not able to install gitolite" crowd.
    
    As a bonus, though, I ended up making proper, hyper-linked, TOCs for
    most of the docs, and moved a whole bunch of stuff around.  Also finally
    got some of the ssh stuff over from my git-notes repo because it really
    belongs here.
  2. (minor)

    authored
  3. *try* to make upgrades resilient to format changes (pkg maintainers p…

    authored
    …lease read)
    
    the commits leading up to v1.5 caused the data format to change (we
    added a rule sequence number).
    
    This in turn caused a problem for people who may have installed using
    the "system install / user setup" mode of install (which includes people
    who used RPM/DEB to install it) -- they would now have to *manually* run
    "gl-setup" once after the rpm/deb upgrade.
    
    This commit *tries* to mitigate this problem by recording a data format
    version number in the compiled output file.  On any access to that file,
    if the version number is not found or is found to be not equal to the
    current version, gl-setup is run again.
    
    The reason I say "*tries*" is that the exact command used to do this is
    a bit of a hack for now.  However, if it works for Fedora and Debian,
    I'm going to leave it at that :)
Commits on May 20, 2010
Commits on May 19, 2010
  1. (important upgrade info here)

    authored
    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.
Commits on May 18, 2010
  1. (big-config) doc fixup

    authored
  2. Revert "allow setperms to override config file permissions"

    authored
    This reverts commit 9612e3a, since it
    is no longer needed as of the rule sequencing changes we just made.
    
    Conflicts:
    
    	src/gl-compile-conf
  3. (big one!) rule sequencing changes!

    authored
    There were 2 problems with rule sequencing.
    
    Eli had a use case where everyone is equal, but some are more equal than
    the others ;-)  He wanted a way to say "everyone can create repos under
    their own names, but only some people should be able to rewind their
    branches".
    
    Something like this would be ideal (follow the rules in sequence for
    u1/u2/u3/u4, and you will see that the "deny" rule kicks in to prevent
    u1/u2 from being able to rewind, although they can certainly delete
    their branches):
    
        @private-owners = u1 u2
        @experienced-private-owners = u3 u4
    
        repo CREATOR/.*
          C   = @private-owners @experienced-private-owners
          RWD = CREATOR
          RW  = WRITERS
          R   = READERS
          -   = @private-owners
          RW+D = CREATOR
    
    In normal gitolite this doesn't work because the CREATOR rules (which
    get translated to "u1" at runtime) end up over-writing the "deny" rule
    when u1 or u2 are the creators.  This over-writing happens directly at
    the "do compiled.pm" step.
    
    With big-config, this does not happen (because @private-owners does not
    get expanded to u1 and u2), but the problem remains: the order of
    picking up elements of repo_plus and user_plus is such that, again, the
    RW+D wins (it appears before the "-" rule).
    
    We fix all that by
    
      - making CREATOR complete to more than just the creator's name (for
        "u1", it now becomes "u1 - wild", which is actually illegal to use
        for real so there's no possibility of a name clash!)
      - maintaining a rule sequence number that is used to sort the rules
        eventually applied (this also resulted in the refex+perm hash
        becoming a list)
Commits on May 16, 2010
  1. (big-config) update doc and rc, allow skipping gitweb/daemon

    authored
    skipping gitweb/daemon has an enormous impact on speed of an admin-push!
Commits on May 14, 2010
  1. @tmatilai

    contrib: Add information about gitolite-tools

    tmatilai authored
    Signed-off-by: Teemu Matilainen <teemu.matilainen@iki.fi>
  2. (big-config) documentation

    authored
  3. (big-config) allow usergroup information to be passed in from outside

    authored
    [Please NOTE: this is all about *user* groups, not *repo* groups]
    
    SUMMARY: gl-auth-commmand can now take an optional list of usergroup
    names after the first argument (which is the username).
    
    See doc/big-config.mkd in the next commit or so
  4. (big-config) compile: fragments in big-config

    authored
    Since it is possible to do all sorts of shenanigans with wildcards and
    repo groups, we
    
      - allow only a fragment called "foo" to set permissions for a group
        called "@foo", in addition to a repo called "foo"
      - forbid defining any groups within a fragment conf.  All "@foo = bar
        baz" must be done in the main config file now.
    
    If this proves too limiting for anyone I'll worry about it then.
  5. @tmatilai

    contrib: Add gitweb example configurations

    tmatilai authored
    Move the example code from doc/3 to contrib/gitweb/ and modify it
    to work with both wildcard and non-wildcard setups.
    
    Signed-off-by: Teemu Matilainen <teemu.matilainen@reaktor.fi>
Something went wrong with that request. Please try again.