Mustafa Orkun Acar writes:
> Hi,
> I have completed my proposal about this project. But in one of the previous
> emails; it says that the aim of the project is not storing configuration data
> in the memory instead of making multiple git_config() calls. I
> also understand the project in this
Yao Zhao writes:
> Moy, thanks for explaining. You said API should be hided. Is that
> means I should indicate an arbitary feature in old version or new
> feature we added should be linked to a manipulation of inner
> structure? And I need to find the connection to make this abstraction?
Sorry,
I think I misunderstand the project as Moy said. I thought the purpose of
project is to store configuration into memory between multiple git calls. Sorry.
Moy, thanks for explaining. You said API should be hided. Is that means I
should indicate an arbitary feature in old version or new feature w
Matthieu Moy writes:
> Why?
>
> (In general, explaining why you chose something is more important than
> explaining what you chose)
Good educational comment. Thanks.
> A tree (AST, Abstract syntax tree) can be interesting if you have some
> source-to-source transformations to do on the configu
Hi,
Yao Zhao writes:
> 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).
I'd actually load the configuration lazily, when Git first requires a
configuration va
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
6 matches
Mail list logo
