Skip to content
Commits on Mar 27, 2012
  1. ssh-authkeys: remove needless map

    someone reported an error on "my $_" (presumably old perl) but I now
    realise the whole map is useless; both the lists concerned have already
    been chomped.
    committed Mar 27, 2012
Commits on Mar 26, 2012
  1. fixup new check-g2-compat, lots of migration related changes...

    aaargh!  I forgot to 'git rm' something despite documenting it to be
    gone and not using it
    committed Mar 26, 2012
  2. aded non-core documentation

    committed Mar 26, 2012
  3. partial-copy fixed...

    ...there was one real bug, plus I had forgotten to put a comented out
    line in the rc file, but most of the rest of the effort was moving the
    test script over.
    oh and I'd also forgotten to move this from 'commands' to 'triggers' :-)
    committed Mar 26, 2012
  4. documentation fixups

    committed Mar 26, 2012
  5. move triggers into their own subdir...

    ...otherwise 'gitolite help' was getting too confusing, mixing up stuff
    that users should not be running directly (even on the server)
    implementation notes:
    those who are worried about the '../triggers/' in various parts of the
    code here, remember you can only do that from a command line on the
    server.  Remote users can only use commands that have been explicitly
    listed in the COMMANDS hash in the rc file.  This means they can't even
    access other commands in the same directory as, say, the 'info' command,
    so a '../' is definitely not going to work.
    committed Mar 26, 2012
  6. make standalone config entries work

    For example, in
        repo foo/..*
            C   =   u1 u2 u3
            RW+ =   CREATOR
            RW  =   WRITERS
            R   =   READERS
            config hooks.emailprefix = '[%GL_REPO] '
            config  = bar one
        repo foo/u1/..*
            config bar.baz  = frob nitz
    make that last config also work!
    committed Mar 26, 2012
  7. (minor) use 'sts' as the url for the ssh-troubleshooting page

    when g3 becomes "master", the URL in the git info bot won't have to
    committed Mar 26, 2012
Commits on Mar 25, 2012
  1. arguments in rc for triggered programs...

    ...using 'renice' as example and first user
    (also had to re-arrange rc file to a more sensible order)
    committed Mar 25, 2012
  2. warn about test suite clobbering lots of stuff

    (not just ~/.ssh!)
    committed Mar 25, 2012
  3. new check-g2-compat, lots of migration related changes

      - rc differences moved to their own file
      - main g2migr now helps interpret output of check-g2-compat
      - Gitolite::Compat gone; no point...
    committed Mar 25, 2012
Commits on Mar 24, 2012
  1. Q: all doc stuff

    committed Mar 16, 2012
  2. 3 old VREFs moved in,

    untested but they're just update hooks anyway so they should work fine
    committed Mar 24, 2012
  3. list-users acquires an optional repo name patten to speed things up

    but see warnings in usage text.
    committed Mar 23, 2012
  4. external programs can get settings from rc; see below

    non-core programs can get their settings from the rc file also.
    cpu-time is a perl example and desc is a shell example.
    (info is not a good example because it does not use "Gitolite::Easy")
    committed Mar 22, 2012
  5. query-rc learns '-q' option

    committed Mar 23, 2012
  6. (minor) fixup various TODOs and such

    some got junked, some were already done or got done, and some were
    converted into actual todo items in the 'todo' file.
    committed Mar 22, 2012
  7. enhance the projects.list updater to look at 'gitweb.*' config settin…

    …gs also
    (not just 'R = gitweb')
    Can you tell I really, really, don't want anything to do with gitweb and
    daemon to be part of gitolite *core*?  :-)
    committed Mar 22, 2012
  8. run compat checks when old rc found

    (also removed legacy-delegation sugar script)
    committed Mar 22, 2012
  9. minor changes to testing setup

    committed Mar 21, 2012
  10. cleaned up logging quite a bit; details:

      - a remote "id" (usually the IP) is generated and logged on the first
        log message in a "transaction"
      - speaking of which, a new "transaction ID" is logged that stays the
        same for each input command/invocation, tying together all the
        spawned commands
      - so now time stamps can be generated each time they are needed,
        rather than re-use the one at the beginning
      - log messages have a keyword at the start now
            remote, (create), check1 -- from gitolite-shell
            update, check2 -- from update
            post-up -- from post-update
            command -- from gitolite
            die, system -- from anywhere
    committed Mar 21, 2012
  11. trigger POST_CREATE from user actions

      - uncomment the POST_CREATE section in rc by default now
      - have perms call 'gitolite trigger POST_CREATE'
    committed Mar 21, 2012
Something went wrong with that request. Please try again.