git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bo Yang <struggleyb.nku@gmail.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org, Thomas Rast <trast@student.ethz.ch>
Subject: Re: [GSoC 2010] The 1st week
Date: Tue, 25 May 2010 16:58:11 +0800	[thread overview]
Message-ID: <AANLkTilEoK-CZR8C16ageafSnA_TNyp3nXHVAm67_LS3@mail.gmail.com> (raw)
In-Reply-To: <20100525062457.GB10898@coredump.intra.peff.net>

On Tue, May 25, 2010 at 2:24 PM, Jeff King <peff@peff.net> 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

  reply	other threads:[~2010-05-25  8:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-24 14:57 [GSoC 2010] The 1st week Bo Yang
2010-05-25  6:24 ` Jeff King
2010-05-25  8:58   ` Bo Yang [this message]
2010-05-25  9:06     ` Jeff King
     [not found] ` <15312_1274768714_4BFB6D49_15312_1749_67_20100525062457.GB10898@coredump.intra.peff.net>
2010-05-25  7:26   ` Albert Krawczyk

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=AANLkTilEoK-CZR8C16ageafSnA_TNyp3nXHVAm67_LS3@mail.gmail.com \
    --to=struggleyb.nku@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    --cc=trast@student.ethz.ch \
    /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).