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

Re: [GSoC 2010] The 1st week

From
Jeff King <peff@peff.net>
Date
May 25, 2010, 06:24 UTC
Message-ID
<20100525062457.GB10898@coredump.intra.peff.net>
In-Reply-To
<AANLkTikSafHBj7VwjwjTVeW3ohL60dOp4sKfZW_vZzCM@mail.gmail.com>
On Mon, May 24, 2010 at 10:57:15PM +0800, Bo Yang wrote:
Show 11 quoted lines
> 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.

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. :)

-Peff
Previous: Bo YangNext: Bo Yang
Message 2 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.