git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [GSOC 2014]idea:Git Configuration API Improvement

From
Michael Haggerty <mhagger@alum.mit.edu>
Date
Mar 20, 2014, 08:47 UTC
Message-ID
<532AAB39.3010507@alum.mit.edu>
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/
Previous: Yao ZhaoNext: Matthieu Moy
Message 2 of 7 in “[GSOC 2014]idea:Git Configuration API Improvement”
  1. Yao ZhaoMar 20, 2014
  2. Michael HaggertyMar 20, 2014
  3. Matthieu MoyMar 20, 2014
  4. Junio C HamanoMar 20, 2014
  5. Yao ZhaoMar 20, 2014
  6. Matthieu MoyMar 21, 2014
  7. Matthieu MoyMar 21, 2014

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.