Hosting git repositories -- Gitolite allows you to setup git hosting on a central server, with very fine-grained access control and many (many!) more powerful features.
Go to file
Sitaram Chamarty d8df4a9344 git-config bugfix + backward compat breakage in usage of 'config'
(1) the backward compat breakage: you can't create empty-valued config
    keys anymore.  That is, you can't do the eqvt of the following shell
    command using gitolite

        git config foo.bar ""

(2) fixed a bug where this:

        repo foo
            config foo.bar =

    when queried using

        gitolite git-config -r foo .

    would return even the empty valued ones, which -- remember! -- are
    not supposed to exist anymore.

    Fixing this bug allows situations like this to not show the admin
    repo in gitweb:

        repo [a-z].*
            config gitweb.owner = P-h B

        repo gitolite-admin
            config gitweb.owner =

----

background...

Somewhere in g3 (well actually in 057506b), we lost the ability to
distinguish
    config foo.bar  =   ""
from
    config foo.bar =

I decided that conflating them is more intuitive for most people,
because a survey [1] revealed that no one seemed to want the equivalent
of the following shell command:

----

[1] ...of a (small prime greater than 1) number of people on #git
2012-05-04 17:30:22 +05:30
doc git-config bugfix + backward compat breakage in usage of 'config' 2012-05-04 17:30:22 +05:30
src git-config bugfix + backward compat breakage in usage of 'config' 2012-05-04 17:30:22 +05:30
t BSD compat changes 2012-04-28 22:58:09 +05:30
check-g2-compat (some minor changes) 2012-04-05 21:31:59 +05:30
convert-gitosis-conf (mostly) doc changes 2012-04-10 15:41:32 +05:30
COPYING add COPYING file 2012-04-26 16:06:03 +05:30
dot.pl Q: all doc stuff 2012-03-24 18:22:11 +05:30
install install should fail more gracefully if the '-ln' directory does not exist 2012-04-22 22:43:27 +05:30
README.mkd (some docfixes) 2012-04-21 22:29:56 +05:30

Gitolite README

Github users: please read the "wiki" link at the top of the page before submitting issues or pull requests.


If you're reading this on the main gitolite page on github, several IMPORTANT CHANGES have happened to gitolite:

  1. A competely re-written version of gitolite has been pushed to the "master" branch, and is now the actively maintained and supported software. Do NOT try to merge this with your old "master" branch!

    The main page leads to several useful starting points. The table of contents is a much more meaningfully ordered/structured list of links (instead of putting them in alphabetical order of the filename, like in g2!)

    If you are an existing (g2) user and wish to migrate, you MUST read this.

  2. Versions v2.x are on branch "g2". It will be supported for security issues and serious bugs in core functionality, but not for anything less critical. Versions v1.x are completely unsupported now. (Documentation links for this version are here and here).


License information for code and documentation is at the end of doc/index.mkd (or you can read it online here).