Re: gsoc - Better git log --follow support

From: Michał Łowicki <mlowicki@gmail.com>
Date: Apr 13, 2011, 21:04 UTC
Message-ID: <BANLkTik7t=Tfh_Y_+swnaAWyetfy8MU6VA@mail.gmail.com>
In-Reply-To: <AANLkTi=n7e70UqYU+6wpG4cu95fsg39tVM6=7fpfdZFz@mail.gmail.com>

Hi! This is the first plan for this gsoc project. Jonathan Nieder described me how --follow works and pointed me to a lot of sources for studying. He also suggested where I should start a how it should look like (thanks for that).

25.04 - 15.06
1) study the revision walking code
    * understand its stages,
    * improve Documentation/technical/api-revision-walking.txt (it
doesn't explain revision walking code stages so I could save others
some time in the future)

2) study the pathspec matching + limiting and rename detaction API
    * possiblity to update/improve documenation here as well

3) figure out what state --follow will need to maintain, where it will
fit into the revision walking process and design new architecture for
it

16.06 - 26-08
4) implementation

I plan to spend about 2 months for the first 3 points. It's all about poking the right developers and sending question to the mailing list. I'll try to send some updates soon when I get through some basic lecture and the most important code.

Any suggestions/ideas are as always welcome. Be prepare for many questions from my side :)

Greetings, Michał Łowicki