From: Dragos Foianu <dragos.foianu@gmail.com>
To: git@vger.kernel.org
Cc: Dragos Foianu <dragos.foianu@gmail.com>
Subject: [GSoC 2014] git config API improvements
Date: Mon, 17 Mar 2014 00:27:58 +0200 [thread overview]
Message-ID: <1395008878-18677-1-git-send-email-dragos.foianu@gmail.com> (raw)
Hello,
My name is Dragos Foianu and I am an undergraduate student at University Politehnica of Bucharest in Romania. This is my final year and I'm planning on doing something more exciting than the simple
assignments I get from the university.
I have been working with git for quite some time now and I'm currently using it for my diploma project. It was annoying at first but now I love it and it has helped me many times in the past. I wanted to
contribute to the project and I feel that GSoC 2014 is the perfect opportunity for this.
I am primarily interested in the "git config API improvements" project. I have glanced over the code in order to get an idea of how git-config currently works. The project idea page gives a very good
description of what is desired. Caching and retrieving values by name sounds to me like a hint to use a hashtable-like data structure. Conveniently, there is already a hashmap implementation in git and
even more conveniently, there is a cache implementation that uses that data structure. So that part is fairly straightforward.
I have a question, however: how would I go about detecting when a cache invalidation is necessary? Considering I have read a configuration file and cached the configuration in memory, what can trigger
one of the existing cache entries to be invalidated?
That is all I have to ask for now. I will look over the code during the next few days to get the bigger picture and submit my application. At [1] you can find my microproject patch. I am eagerly awaiting
for any questions you might have.
All the best,
Dragos
[1] http://thread.gmane.org/gmane.comp.version-control.git/244210
reply other threads:[~2014-03-16 22:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1395008878-18677-1-git-send-email-dragos.foianu@gmail.com \
--to=dragos.foianu@gmail.com \
--cc=git@vger.kernel.org \
/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).