From: Eli Barzilay <eli@barzilay.org>
To: git@vger.kernel.org
Subject: Re: gitweb problem?
Date: Mon, 01 Mar 2010 23:40:08 -0500 [thread overview]
Message-ID: <m3vddfuyjb.fsf@winooski.ccs.neu.edu> (raw)
In-Reply-To: m37hpwma9u.fsf@localhost.localdomain
Jakub Narebski <jnareb@gmail.com> writes:
> BTW. the first line number is in git_cmd invoked (called) from
> git_get_project_config.
(Oh yeah, I forgot about that one, sorry.)
> [...]
>
> The last solution, while requiring most work, has the advantage of
> being able to do override via user (~apache/.gitconfig) or system
> (/etc/gitconfig) gitweb config file. But I am not sure if it is
> worth it...
Thanks for the fix! As for the point above, isn't the whole point of
the feature system to do this kind of toplevel configuration possible?
(If so, it sounds like a concrete explanation for why it's not worth
the effort: it only makes it possible to specify the defaults in a
toplevel .gitconfig file, which could be nice but probably confusing.)
--
((lambda (x) (x x)) (lambda (x) (x x))) Eli Barzilay:
http://barzilay.org/ Maze is Life!
prev parent reply other threads:[~2010-03-02 4:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-01 6:54 gitweb problem? Eli Barzilay
2010-03-01 10:24 ` Jakub Narebski
2010-03-01 11:51 ` Eli Barzilay
2010-03-01 13:40 ` Jakub Narebski
2010-03-01 21:51 ` [PATCH] gitweb: Fix project-specific feature override behavior Jakub Narebski
2010-03-02 4:40 ` Eli Barzilay [this message]
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=m3vddfuyjb.fsf@winooski.ccs.neu.edu \
--to=eli@barzilay.org \
--cc=git@vger.kernel.org \
/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).