From: Jakub Narebski <jnareb@gmail.com>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [RFC] gitweb: Add committags support (take 2)
Date: Wed, 6 Dec 2006 21:35:44 +0100 [thread overview]
Message-ID: <200612062135.44658.jnareb@gmail.com> (raw)
In-Reply-To: <7vpsaw3iyp.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
> Jakub Narebski <jnareb@gmail.com> writes:
>
>> By the way, what is the formal structure of the config file? Perhaps
>> something like the notation used in RFC?
>
> Is there an RFC for .INI format?
I don't think INI is standarized at all. The format of INI files is not
well defined. That's why I'd like to know exact format of git INI-like
config file format.
But what I meant was description of git config file in (used by RFCs)
augmented Backus-Naur Form (BNF) - RFC 4234.
>> 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?
>
> If you are asking about [gitweb] stanza and (seemingly
> overlapping) [gitweb "foo"] stanza, we already have prior
> examples:
>
> [diff]
> color = auto
> [diff "color"]
> whitespace = blue reverse
>
> so your example in the above would be legal (the dash in
> 'message-id' part might be questionable, though).
That's what I was asking for. Thanks for an explanation.
--
Jakub Narebski
prev parent reply other threads:[~2006-12-06 20:33 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
2006-12-06 19:47 ` Junio C Hamano
2006-12-06 20:35 ` Jakub Narebski [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=200612062135.44658.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).