From: "Catalin Marinas" <catalin.marinas@gmail.com>
To: "Yann Dirson" <ydirson@altern.org>
Cc: "GIT list" <git@vger.kernel.org>
Subject: Re: StGIT and repo-config
Date: Thu, 25 Jan 2007 23:45:45 +0000 [thread overview]
Message-ID: <b0943d9e0701251545w1b34a0dcg545eeab08d767e38@mail.gmail.com> (raw)
In-Reply-To: <20070125225512.GF4083@nan92-1-81-57-214-146.fbx.proxad.net>
On 25/01/07, Yann Dirson <ydirson@altern.org> wrote:
> I'm trying to get StGIT to work with git's config information.
> Currently, the stgit.config stuff uses a generic ConfigParser, which
> I'm not sure is adequate for the work:
There are some drawbacks indeed and it currently reads the configs and
transforms them slightly before passing them to ConfigParser. StGIT
initially had its own config files (git config came a bit later).
It would be good to have this re-written. It is even better to use
something like config.get('user.name') rather than config.get('user',
'name') as in ConfigParser.
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).
For the options setting, it shouldn't probably need to use --global.
As above, these options should be cached in the dictionary as well.
--
Catalin
next prev parent reply other threads:[~2007-01-25 23:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-25 22:55 StGIT and repo-config Yann Dirson
2007-01-25 23:45 ` Catalin Marinas [this message]
2007-01-25 23:58 ` Johannes Schindelin
2007-01-26 17:53 ` Yann Dirson
2007-01-26 22:51 ` Catalin Marinas
2007-01-26 23:12 ` Johannes Schindelin
2007-01-27 10:33 ` Yann Dirson
2007-01-28 23:30 ` Catalin Marinas
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=b0943d9e0701251545w1b34a0dcg545eeab08d767e38@mail.gmail.com \
--to=catalin.marinas@gmail.com \
--cc=git@vger.kernel.org \
--cc=ydirson@altern.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).