From: Michael Haggerty <mhagger@alum.mit.edu>
To: Yao Zhao <zhaox383@umn.edu>
Cc: Matthieu.Moy@grenoble-inp.fr, peff@peff.net, git@vger.kernel.org
Subject: Re: [GSOC 2014]idea:Git Configuration API Improvement
Date: Thu, 20 Mar 2014 09:47:53 +0100 [thread overview]
Message-ID: <532AAB39.3010507@alum.mit.edu> (raw)
In-Reply-To: <1395300220-7540-1-git-send-email-zhaox383@umn.edu>
On 03/20/2014 08:23 AM, Yao Zhao wrote:
> Third one is about when to write back to file, I am really confused
> about it. I think one way could be when user leave git repository
> using "cd" to go back. But I am not sure if git could detect user
> calls "cd" to leave repository.
I don't understand. The cache would be in memory, and would only live
as long as a single "git" process. Within that process, if somebody
wants to change the config, they might (for example) call one function
to lock the config file, a second function to change the value(s) in
memory, and then a third function to flush the new config out to disk
and unlock the config file again. The cache would usually only live for
milliseconds, not minutes/hours, so I don't think your question really
makes sense.
Michael
--
Michael Haggerty
mhagger@alum.mit.edu
http://softwareswirl.blogspot.com/
next prev parent reply other threads:[~2014-03-20 8:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-20 7:23 [GSOC 2014]idea:Git Configuration API Improvement Yao Zhao
2014-03-20 8:47 ` Michael Haggerty [this message]
2014-03-20 9:10 ` Matthieu Moy
2014-03-20 17:36 ` Junio C Hamano
2014-03-20 21:15 ` Yao Zhao
2014-03-21 8:23 ` Matthieu Moy
[not found] ` <CAP4BmmHAuWYgeMvk11ywJ5eXQunCWPepGEE3UTKfiVn60RQVrw@mail.gmail.com>
2014-03-21 13:42 ` Matthieu Moy
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=532AAB39.3010507@alum.mit.edu \
--to=mhagger@alum.mit.edu \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=zhaox383@umn.edu \
/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).