git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[GSoC 2010] The 1st week

From
Bo Yang <struggleyb.nku@gmail.com>
Date
May 24, 2010, 14:57 UTC
Message-ID
<AANLkTikSafHBj7VwjwjTVeW3ohL60dOp4sKfZW_vZzCM@mail.gmail.com>
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
Next: Jeff King
Message 1 of 5 in “[GSoC 2010] The 1st week”
  1. Bo YangMay 24, 2010
  2. Jeff KingMay 25, 2010
  3. Bo YangMay 25, 2010
  4. Jeff KingMay 25, 2010
  5. Albert KrawczykMay 25, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.