List for cgit developers and users
 help / color / mirror / Atom feed
Subject: [PATCH 0/2] Git-Config Parsing during scan-path
Date: Sun,  7 Oct 2012 23:23:45 +0200	[thread overview]
Message-ID: <1349645027-22007-1-git-send-email-necoro@necoro.net> (raw)

Some time ago, Jamie sent a patch to this list that allows to parse the git
config on scan-path [1]. The main use-case is a nice integration with gitolite
instead of the 'one workaround per option' as it is handled now
(enable-gitweb-*).

As Jason had asked to resend non-applied patches, I took the chance to port the
patch to the current master and to update the documentation.

Changes wrt the old patch:

* Use "cgit" as gitconfig section instead of "repo" -- the latter is too generic
imho and might lead to problems in the future.

* Removed some obscure Apache hint that seemed to be out of context.

* Update example gitolite.conf to recent gitolite-3 syntax.

* Pointed out that it works perfectly fine together with the (now) existing
'enable-gitweb-*' stuff.

[1] http://hjemli.net/pipermail/cgit/2011-November/000414.html

- Ren?

Ren? 'Necoro' Neumann (2):
  Read "cgit.*" settings from gitconfig.
  Documentation for the gitconfig sourcing.

 cgit.c       |    3 +++
 cgit.h       |    1 +
 cgitrc.5.txt |   47 +++++++++++++++++++++++++++++++++++++++++++++++
 scan-tree.c  |   19 +++++++++++++++----
 4 files changed, 66 insertions(+), 4 deletions(-)

-- 
1.7.8.6





             reply	other threads:[~2012-10-07 21:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-07 21:23  [this message]
2012-10-07 21:23 ` [PATCH 1/2] Read "cgit.*" settings from gitconfig 
2012-10-08 15:14   ` jamie.couture
2012-10-08 15:19     ` Jason
2012-10-08 15:24       ` 
2012-10-08 15:25         ` Jason
2012-10-07 21:23 ` [PATCH 2/2] Documentation for the gitconfig sourcing 
2012-10-08 21:27 ` [PATCH 0/2] Git-Config Parsing during scan-path Jason
2012-10-09  9:30   ` 
2012-10-09 11:40     ` Jason
2012-10-09 12:07       ` 
2012-10-09 12:22         ` Jason
2012-10-09 11:02   ` jamie.couture

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1349645027-22007-1-git-send-email-necoro@necoro.net \
    --to=cgit@lists.zx2c4.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).