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
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html