On Tue, May 25, 2010 at 2:24 PM, Jeff King <peff@xxxxxxxx> wrote: > On Mon, May 24, 2010 at 10:57:15PM +0800, Bo Yang wrote: > >> 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. > > You didn't mention > > 4. Contributing to other discussion of --follow on the list. > > It is a small thing, perhaps, but I am very happy to see a GSoC student > actively participating in the community. Thanks! :) > Speaking of which, I haven't finished polishing the --follow patches > from our earlier thread. I was taking a look at making history > simplification (including --parents) work. Are you going to be doing any > work on that this summer? If so, I will probably just drop it for now > and let you deal with it. :) Yeah, the line level browser will touch the parents rewriting things and I think the feature of line level history is a super-set of the '--follow' things, so you can leave it with me. And in my plan, I will complete this in next month. :) 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