Commits on Jun 1, 2011
  1. v2.0.2

    committed Jun 1, 2011
  2. (sskm) document courtesy Jeff Mitchell

    I'd originally written some minimal documentation for this ADC, but I
    liked Jeff's version so much that I borrowed it, added the final section
    ("important notes for the admin"), made a few other minor fixups, and
    then happily ditched my version.
    committed Jun 1, 2011
  3. (sskm) hush output from internal git commands

    (the ones that require GL_BYPASS_UPDATE_HOOK to be set are done slightly
    differently because I just didn't want all the hassle of saving and
    restoring that variable on the perl side)
    committed May 27, 2011
  4. (sskm) not finding a key in the list is not always fatal...

    [caught by Jeff...]
    committed May 26, 2011
  5. (sskm) self-service key management -- new adc

    based on a discussion with Jeff from the KDE team; see doc for more.
    committed Jun 1, 2011
Commits on May 28, 2011
  1. oopsies... should be checking for "-x" not just "-f or -l" to chain a…

    … hook
    it was trying to execute a broken symlink!  (Thanks to Jeff of KDE for
    catching this)
    committed May 28, 2011
  2. (here's more proof that writing code is easier...)

    streamline the README and the install doc a fair bit, especially make
    'from-client' install deprecated, and relegate it to an Appendix.
    committed May 28, 2011
  3. make gl-system-install easier to run

    make the arguments optional (with documented defaults) plus they need
    not exist a priori, reducing one command (the silly mkdir!) that the
    user has to run.
    All this is preparatory to deprecating the from-client method.  We've
    even switched the test suite to 'non-root' method now
    committed May 27, 2011
  4. (minor) doc tweaks

    committed May 16, 2011
Commits on May 25, 2011
  1. make projects.list (and some other files) writes atomic

    The KDE folks have a projects.list file that gets picked up by rsync and
    sent elsewhere in some cron-ish manner.  They noticed that occasionally
    the file that went across was truncated, which indicates that maybe it
    got picked up while it was still being written.
    oh and this change also affects any files that get written using
    committed May 24, 2011
Commits on May 24, 2011
  1. (minor) make htpasswd use md5 passwords

    (thanks to yoonique dot net at gmail; he also tested that files with
    some normal and some md5 passwords, such as would happen on an upgrade,
    work fine)
    committed May 24, 2011
Commits on May 23, 2011
  1. (minor fix to t67)

    committed May 23, 2011
Commits on May 19, 2011
Commits on May 12, 2011
  1. (doc) ADCs now have an overview doc, plus...

      - repo-deletion is now a proper doc
      - other doc enhancements and clarifications
    committed May 8, 2011
Commits on May 10, 2011
Commits on May 8, 2011
  1. su-getperms and su-setperms

    committed May 8, 2011
Commits on May 5, 2011
  1. (doc) Initial entry of gitolite-gitweb-http-backend documentation

    Initial entry of markdown documentation as generated by pod2markdown.
    Note addition of table-of-contents and appropriate anchors
    Signed-off-by: Christopher M. Fuhrman <>
    [some formatting type changes done by Sitaram]
    cfuhrman committed with May 4, 2011
Commits on May 4, 2011
  1. forcibly set user.{name,email} if needed

    git 1.7.4+ insists on these two being defined.  So I reduce my support
    load by forcing them if they were not set.
    Much easier than explaining to people what should be obvious from the
    error message.
    committed May 4, 2011
Commits on May 2, 2011
  1. new adc to allow deleting a branch that you created; see below

    The need for this comes about as follows:
      - a project may allow its developers "RWC" (or "RW+C") so that they
        can create feature branches when needed.  Note that these are
        *feature* branches, so they can't use the "personal branches"
        mechanism that gitolite already has.
      - the developers are *not* given RWCD (or RW+CD) to prevent accidental
        deletion of an important branch.  Branch *deletion* is something
        that only a few trusted admins can do.
      - as a result, there are sometimes situations where a developer
        creates a misnamed branch and then has to ask the admins to help get
        rid of it.
    What the KDE folks wanted was a way to allow the creator of a branch to
    be able to delete it.  In addition, they needed this allowed only for a
    fixed duration after the creation of a branch, not forever (for the same
    reason they don't get RWCD, to prevent accidents).
    These are my reasons why this feature is implemented as an ADC instead
    of being "in core":
      - we'd need additional syntax to differentiate this special case
        (which is sort of in between RWC and RWCD, if you think about it).
        I'm reluctant to complicate the syntax further for something that is
        only occasionally needed.
      - we'd need either (a) code to parse the log files, or, (b) code to
        maintain "who created this ref" on every push that creates a ref.
          - parsing the log files is too kludgy and inelegant to be in core,
            not to mention potentially very slow for really large projects
          - code to maintain the a history of "who created this ref" is too
            cumbersome, especially because of the need to expire old entries
            after a time.
    committed May 1, 2011
Commits on Apr 30, 2011
  1. v2.0.1

    committed Apr 30, 2011
Commits on Apr 28, 2011
  1. "hooklets" -- play nice with any number of site-local 'update' hooks

    (yes, I made up the name.  Deal with it!)
    committed Apr 25, 2011
Commits on Apr 24, 2011
  1. (minor doc fixes)

    committed Apr 24, 2011
Commits on Apr 3, 2011
  1. gl-system-install: optional 4th arg to help packagers

    (buildroot in RPM-speak, DESTDIR in DEB-speak)
    based on a patch sent by Francis Galiegue (fgaliegue at gmail)
    committed Apr 3, 2011
Commits on Apr 1, 2011
  1. allow the include statement to use globs

    (bonus: we now have a test case for "include" itself, should it ever
    decide to take an unplanned vacation!)
    committed Apr 1, 2011
Commits on Mar 30, 2011
  1. Make limit on number of repos displayed by info with GL_BIG_CONFIG co…

    [doc added by Sitaram]
    dylex committed with Mar 24, 2011
Commits on Mar 25, 2011
  1. minor docfix to smart http doc

    committed Mar 25, 2011
Commits on Mar 21, 2011
  1. more mirroring changes...

    the first one is commented clearly enough, the second one is a pure bug
    (though it wouldn't have affected anything except for the ultra-paranoid
    "fsckObjects" config var not being set; no biggie...)
    committed Mar 16, 2011
  2. mirror-shell fix: setup GL_RC; post-update needs it

    Jos Houtman committed with Mar 15, 2011
  3. make REPO_BASE absolute early

    $ENV{GL_REPO_BASE_ABS} is meant to point to the same directory as
    $REPO_BASE, except it is meant to be passed to hooks, ADCs and other
    child programs.  And since you can't be sure where the child program
    starts in, this became an absolute path.
    Gradually, however, I started using it wherever I needed an absolute
    path (mostly in code that jumps around various directories to do stuff).
    Which is silly, because there's no reason $REPO_BASE cannot also be made
    an absolute, even if the rc file has a relative path.
    So that's what I did now: made $REPO_BASE absolute very early on, and
    then systematically changed all uses of the longer form to the shorter
    form when appropriate.  And so the only thing we now use the longer one
    for is to pass to child programs.
    (Implementation note: The actual change is not very big, but while I was
    about it I decided to make the test suite able to test with an absolute
    REPO_BASE also, which is why the commit seems so large.)
    This all started with a complaint from Damien Regad.  He had an
    extremely odd setup where his bashrc changed PWD to something other than
    $HOME before anything else ran.  This caused those two variables to
    beceom inconsistent, and he had a 1-line fix he wanted me to apply.
    I generally don't like making special fixes for for non-standard setups,
    and anyway all he had to do was set the full path to REPO_BASE in the rc
    file to get around this.  Which is what I told him and he very politely
    left it at that.
    However, this did get me thinking, and I soon realised I was needlessly
    conflating "relative versus absolute" with "able to be passed to child
    programs".  Fixing that solved his problem also, as a side-effect.
    So I guess this is all thanks to Damien!
    committed Mar 18, 2011