Re: StGIT and repo-config
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- Jan 25, 2007, 23:58 UTC
- Message-ID
- <Pine.LNX.4.63.0701260052590.22628@wbgn013.biozentrum.uni-wuerzburg.de>
- In-Reply-To
- <b0943d9e0701251545w1b34a0dcg545eeab08d767e38@mail.gmail.com>
Hi,
On Thu, 25 Jan 2007, Catalin Marinas wrote:
Show 5 quoted lines
> What I'd like it to have is a single initial call to git-repo-config > --list (in config_setup) and all the options cached in a dictionary (so > that .git/config options would override the global ~/.gitconfig ones). > The dictionary should also be pre-populated with the default values > (only in memory, not going to the config file on disk).
There was another thread, a few days ago, where Jakub proposed an alternative config parser in Perl. Eric Wong even wrote a rather large patch to automatically generate _source_ code for Perl, Python and Ruby.
I then proposed to have a simple --dump option to repo-config, which outputs NUL separated key/value pairs (substituting "true" for keys without -- not with empty! -- values). But somehow the discussion petered out before anything came out of it.
The most important point (to me) which came out of the discussion: It is not at all easy, or straight-forward, to handle multi-vars, i.e. multiple values for the same key.
Ciao, Dscho