From: Jakub Narebski <jnareb@gmail.com>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org, Pasky Baudis <pasky@suse.cz>
Subject: Re: [RFC] gitweb: Add committags support (take 2)
Date: Wed, 6 Dec 2006 20:32:58 +0100 [thread overview]
Message-ID: <200612062032.58706.jnareb@gmail.com> (raw)
In-Reply-To: <7vveko3km4.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
> Jakub Narebski <jnareb@gmail.com> writes:
>
>> 2. Put the configuration in config file, using/like %features support.
>> For example gitweb.committags.<committag name> would hold parameters
>> for <committag>. Committags sequence would be given by sequence of
>> entries in config file. Comittags without options would have sole
>> variable entry (which I think is equivalent to being bool variable
>> and having 1 or 'yes' as value).
>
> I think gitweb.* in $GIT_DIR/config and a config reader in Perl
> are very sensible things to do, and you would need the config
> reader eventually anyway. The longer we postpone it, the more
> we risk the temptation to pollute $GIT_DIR/ with the likes of
> "description", "owner", and "homepage", and I do not think we
> want to make this worse.
By the way, what is the formal structure of the config file? Perhaps
something like the notation used in RFC?
Is it possible (and doesn't crash current git config parser) having
[gitweb]
blame = yes
pickaxe = no
snapshot = bzip2
[gitweb "committags"]
message-id = "http://news.gmane.org/find-root.php?message_id="
mantis = "http://bugs.or.cz/view.php?id="
url
sha1
in the config file?
--
Jakub Narebski
next prev parent reply other threads:[~2006-12-06 19:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-03 23:01 [RFC] gitweb: Add committags support (take 2) Jakub Narebski
2006-12-04 2:38 ` Junio C Hamano
2006-12-04 10:33 ` Jakub Narebski
2006-12-04 10:53 ` Junio C Hamano
2006-12-04 11:33 ` Jakub Narebski
2006-12-05 1:08 ` Junio C Hamano
2006-12-06 12:51 ` Jakub Narebski
2006-12-06 19:11 ` Junio C Hamano
2006-12-06 19:32 ` Jakub Narebski [this message]
2006-12-06 19:47 ` Junio C Hamano
2006-12-06 20:35 ` Jakub Narebski
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=200612062032.58706.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=pasky@suse.cz \
/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).