From: jamie.couture at gmail.com (Jamie Couture)
Subject: enable-git-config=1
Date: Tue, 9 Oct 2012 09:18:52 -0400 [thread overview]
Message-ID: <CAH-DoZ5c0t04Jbfih=MAZWmDPbSZhrBFPP4AyMRCV4i1y5+y6w@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9oNpDRpjUet_-hwssPE+EhCM_VQD0rea2KSVAB8yRRp3w@mail.gmail.com>
Works fine for me.
Thanks.
Tested on CentOS 6 / Fedora 17
On Tue, Oct 9, 2012 at 8:49 AM, Jason A. Donenfeld <Jason at zx2c4.com> wrote:
> Hi all,
>
> After some back and forth with Jamie and Ren?, it looks like the git
> config semantics are going to be like this:
>
> - gitweb.category maps to the cgit repo config key "section"
> - gitweb.description maps to the cgit repo config key "desc"
> - gitweb.owner maps to the cgit repo config key "owner"
> - cgit.* maps to all other cgit repo config keys
>
> This option can be enabled with "enable-git-config=1", and replaces
> all previous "enable-gitweb-*" config keys.
>
> The order of operations is as follows:
>
> - git config settings are applied
> - if the owner is not set from git config, get the owner using the
> usual getpwuid call
> - if the description is not set from git config, look inside the
> static $path/description file
> - if section-from-path=1, override whatever previous settings were
> inside of git config using the section-from-path logic
> - parse $path/cgitrc for local repo.* settings, that override all
> previous settings
>
>
> Please test the jd/gitconfig branch, and let me know how it goes.You
> can read a diff here:
> http://git.zx2c4.com/cgit/commit/?h=jd/gitconfig
>
> Thanks,
> Jason
>
next prev parent reply other threads:[~2012-10-09 13:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-09 12:49 enable-git-config=1 Jason
2012-10-09 13:06 ` enable-git-config=1
2012-10-09 13:09 ` enable-git-config=1 Jason
2012-10-09 13:18 ` jamie.couture [this message]
2012-10-09 20:42 ` enable-git-config=1
2012-10-09 22:10 ` enable-git-config=1 Jason
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='CAH-DoZ5c0t04Jbfih=MAZWmDPbSZhrBFPP4AyMRCV4i1y5+y6w@mail.gmail.com' \
--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).