From: Yao Zhao <zhaox383@umn.edu>
To: mhagger@alum.mit.edu, Matthieu.Moy@grenoble-inp.fr, peff@peff.net
Cc: git@vger.kernel.org, Yao Zhao <zhaox383@umn.edu>
Subject: [GSOC 2014]idea:Git Configuration API Improvement
Date: Thu, 20 Mar 2014 02:23:40 -0500 [thread overview]
Message-ID: <1395300220-7540-1-git-send-email-zhaox383@umn.edu> (raw)
Hello, Michael, Matthieu and peff,
My name is Yao and I am interested in Git Configuration API Improvements listed in idea page in Git. I came up some ideas and really want to discuss them with you.
First is about when to start reading configuration file to cache. My idea is the time user starts call command that need configuration information (need to read configuration file).
Second is about data structure. I read Peff's email listed on idea page. He indicated two methods and I prefer syntax tree. I think there should be three or more syntax tree in the cache. One for system, one for global and one for local. If user indicate a file to be configuration file, add one more tree. Or maybe we can build one tree and tag every node to indicate where it belongs to.
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.
Thank you,
Yao
next reply other threads:[~2014-03-20 7:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-20 7:23 Yao Zhao [this message]
2014-03-20 8:47 ` [GSOC 2014]idea:Git Configuration API Improvement Michael Haggerty
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=1395300220-7540-1-git-send-email-zhaox383@umn.edu \
--to=zhaox383@umn.edu \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=git@vger.kernel.org \
--cc=mhagger@alum.mit.edu \
--cc=peff@peff.net \
/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).