From: "Michał Łowicki" <mlowicki@gmail.com>
To: git@vger.kernel.org
Cc: Jeff King <peff@peff.net>, jrnieder@gmail.com
Subject: Re: gsoc - Better git log --follow support
Date: Wed, 13 Apr 2011 23:04:20 +0200 [thread overview]
Message-ID: <BANLkTik7t=Tfh_Y_+swnaAWyetfy8MU6VA@mail.gmail.com> (raw)
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
next prev parent reply other threads:[~2011-04-13 21:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-19 19:24 gsoc - Better git log --follow support Michał Łowicki
2011-03-19 21:57 ` GSoC - Better "git log --follow" support Jakub Narebski
2011-03-21 12:24 ` gsoc - Better git log --follow support Jeff King
2011-03-22 23:23 ` Michał Łowicki
2011-03-23 16:20 ` Jeff King
2011-03-23 16:58 ` Junio C Hamano
2011-03-23 17:06 ` Jeff King
2011-03-23 18:12 ` Junio C Hamano
2011-03-23 18:22 ` Jeff King
2011-04-13 21:04 ` Michał Łowicki [this message]
2011-04-15 4:06 ` Jonathan Nieder
2011-04-15 19:41 ` Michał Łowicki
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='BANLkTik7t=Tfh_Y_+swnaAWyetfy8MU6VA@mail.gmail.com' \
--to=mlowicki@gmail.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--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).