From: Jeff King <peff@peff.net>
To: Tanay Abhra <tanayabh@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [GSoC] Inquiry about writing config file to disk
Date: Fri, 21 Mar 2014 01:19:41 -0400 [thread overview]
Message-ID: <20140321051941.GA31161@sigill.intra.peff.net> (raw)
In-Reply-To: <loom.20140320T181941-0@post.gmane.org>
On Thu, Mar 20, 2014 at 05:25:22PM +0000, Tanay Abhra wrote:
> I have gone through commit.c, builtin/commit.c and api-config.txt but one
> thing I cannot find is which functions handle writing config file to disk
> after adding a new variable,value pair(for example git config my.option
> true) . It is also marked TODO on the api-config.txt file. Can somebody help
> me , I just want the starting function and will trace the function calls
> after that.
Try starting in cmd_config (in builtin/config.c), the main entry point
for running "git config", and you should be able to trace it from there.
The main logic ends up in the git_config_set_* functions.
-Peff
prev parent reply other threads:[~2014-03-21 5:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-20 17:25 [GSoC] Inquiry about writing config file to disk Tanay Abhra
2014-03-21 5:19 ` Jeff King [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=20140321051941.GA31161@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=tanayabh@gmail.com \
/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).