Hi,
This is the first week of gsoc 2010 coding phrase, and it is a good
time to summary the previous work and make a plan for the following
two weeks.
What's done:
1. Get familiar with Git code base and have read the code of 'git
blame', revision walk, 'git log'.
2. Try to make some patches for git:
1. * by/blame-doc-m-c (2010-05-06) 1 commit, in 'next'
2. * by/log-follow (2010-05-10) 4 commits, in 'next'
3. the '--graph improvement', in discuss and I think ready for inclusion.
3. Start to write some code for the line level browser feature. And it
is in the 'playaround' branch in http://repo.or.cz/w/line.git . Now,
the code can parse multiple line ranges for multiple files in only one
revision.
What's following next 2 weeks:
In next 2 weeks, I will try to make up a version of line level browser
that supports code modification trace and this version will print all
the diff hunks that touch the interesting lines.
Regards!
Bo
--
My blog: http://blog.morebits.org
--
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