This two-in-one series is response to Junio's concerns about being backwards-incompatibile and different ways of solving "system-wide policy" problem. Patches 2/2 version A and 2/2 version B are mutually exclusive. Junio, you would have to choose which one to include. Drew, is the solution proposed in version A (making it easy to include system-wide config in per-instance config) acceptable solution? Table of contents: ~~~~~~~~~~~~~~~~~~ [PATCH 1/2] gitweb: Refactor reading and parsing config file into [PATCHv1 2/2 (version A)] gitweb: Mention read_config_file in gitweb/README [PATCHv3 2/2 (version B)] gitweb: Use /etc/gitweb.conf even if gitweb_conf.perl exist Shortlog: ~~~~~~~~~ Jakub Narebski (2): gitweb: Refactor reading and parsing config file into read_config_file gitweb: Mention read_config_file in gitweb/README or Jakub Narebski (2): gitweb: Refactor reading and parsing config file into read_config_file gitweb: Use /etc/gitweb.conf even if gitweb_conf.perl exist Diffstat: ~~~~~~~~~ gitweb/README | 10 ++++++++++ gitweb/gitweb.perl | 28 ++++++++++++++++++++-------- 2 files changed, 30 insertions(+), 8 deletions(-) or gitweb/INSTALL | 8 +++++--- gitweb/README | 2 +- gitweb/gitweb.perl | 29 +++++++++++++++++++++-------- 3 files changed, 27 insertions(+), 12 deletions(-) -- 1.7.5 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html