Skip to content


Subversion checkout URL

You can clone with
Download ZIP
Commits on Dec 29, 2012
  1. v3.3

  2. perms batch mode confuses; print something to help

    What happens is that running
        ssh git@host perms reponame
    appears to hang, since it is waiting for STDIN.  I added a message to
    help, since we don't want users losing files accidentally!
    (The other alternative is to add a specific option for batch mode, but
    this is backward incompatible for people who have scripts that may be
    doing this).
    thanks to Caleb Cushing for catching this
    The "make sure Ctrl-C gets caught" thing needs some explanation.
    Without it, a user could inadvertently lose his gl-perms file if he ran
    the command in batch mode.  You'd think that the Ctrl-C would hit the
        for (<>) {
    line and bail, but it manages to reach the
        _print( $pf, @a );
    line somehow.  Even trapping SIG INT does not help.
    I suspect it is to do with how signals are propagated by ssh across a
    "no-pty" session, but am not sure.
  3. bug fix: perms propagation to slaves...

    Sometime after v3.2, I fixed what looked like an information disclosure
    issue, where a user could determine if an arbitrary repo existed or not,
    even if he had no rights to see the repo.  This was:
        96cc2ea "new features relating to creating wild repos:"
    Unfortunately, this appears to have broken gl-perms propagation to
    slaves, because now running "perm -c" on an existing repo dies!
    If you run
        git diff 96cc2ea^ <this commit> -- src/commands/perms
    you'll see how simple the fix *should* have been :-(
  4. 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!)
Commits on Dec 19, 2012
  1. 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!
  2. CREATOR need only be a "word" in wild repo patterns

    this was a v2 compat breakage, caught by Dominik Schäfer
    (schaedpq at gmail)
Commits on Dec 14, 2012
  1. 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
  2. (minor) macro buglets

      - allow parameter-less macros
      - allow macro body to start on next line
  3. new trigger: update-gitweb-daemon-from-options

    another way to update gitweb and daemon access lists
Commits on Dec 9, 2012
  1. @csware

    Set Content-Type to text/plain for gitolite commands over http

    csware committed with
    Explicitly set "Content-Type: text/plain" for gitolite commands when
    issued over http, so that it is possible to see the output with normal
    (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 <>
Commits on Dec 7, 2012
  1. (minor) lint had syntax errors

    thanks to xcat on #gitolite for catching it
    (shows you how often it gets used I guess!)
Commits on Dec 5, 2012
  1. bugfix: don't delete description file when running perms

    thanks to drue on #gitolite for catching it
Commits on Dec 4, 2012
  1. a few minor changes

      * minor typos
      * perltidy on Tsh
      * a minor optimisation to "do" in gl-conf
      * remove inapplicable caveat in fork command
Commits on Nov 28, 2012
  1. 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
  2. oops; hashes were getting printed twice in certain cases...

    harmless but wasteful
Commits on Nov 27, 2012
  1. @stephen-palmer

    Fixed bug in lock script

    stephen-palmer committed with
    the unlock command was not checking the correct hash key to match
    the user name
Commits on Nov 22, 2012
  1. 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
  2. @skoslowski
  3. minor fixups to some non-core programs

    (following a bit of a doc shakeup)
Commits on Nov 21, 2012
Commits on Nov 19, 2012
Commits on Nov 14, 2012
  1. v3.2

  2. Uggh; horrible inner loop screwing up all performance :-(

    This might actually make the redis version unnecessary for most people!
    And if it does, well shame on me for not instrumenting things at a more
    granular level before going all "oh we need a cache!"
    [In my defense, I blame redis for being such a sweet little tool that I
    felt compelled to use it somehow!]
    t/sequence failed because the test itself was in error; fixed.
Commits on Nov 13, 2012
  1. gl-conf must be created even if the repo para has only config lines

    gitolite tester committed
    (i.e., no access rules but only config lines)
Commits on Nov 10, 2012
Commits on Nov 9, 2012
Commits on Nov 8, 2012
  1. some minor rearrangements of code...

    why?  now that would be telling!
Commits on Nov 7, 2012
  1. move %GL_REPO and %GL_CREATOR substitution into core

    see usage example at the end of src/triggers/upstream
Commits on Nov 6, 2012
  1. make sure gl-perms exists, even if it is empty...

    I expect this to help if we optimise the rule generation by caching.
Commits on Oct 31, 2012
Commits on Oct 29, 2012
  1. @tianon
Something went wrong with that request. Please try again.