[GSoC Update] The 7th week

[GSoC Update] The 7th week

[Bo Yang]

Hi all,

    This is my status update of the 7th official week of GSoC.
    In the past week, I worked hard parallelly on two branches, one is
the parent rewrite feature and the other is the basic 'git-log -L'
problem fix. Generally:

    1. parent rewrite: I have finally figure out a version 1 of it and
submit it the list. It contain the basic support for '--graph' option
and I also add a few new test cases for it, also there is a little
document update;
    2. the 'git-log -L' basic feature: I have fixed 2 potential bugs
of it and also try to free the commit_list along with the
cmd_line_log_walk to try to reduce some memory leak.

    And there is an extra commit, which is a little bug fix of
previous 'diff-graph' series. :-)

    What's coming on:


Thanks!
-- 
Regards!
Bo
----------------------------
My blog: http://blog.morebits.org
Why Git: http://www.whygitisbetterthanx.com/

Re: [GSoC Update] The 7th week

[Bo Yang]

On Sun, Jul 11, 2010 at 2:57 PM, Bo Yang <struggleyb.nku@gmail.com> wrote:
> Hi all,
>
>    This is my status update of the 7th official week of GSoC.
>    In the past week, I worked hard parallelly on two branches, one is
> the parent rewrite feature and the other is the basic 'git-log -L'
> problem fix. Generally:
>
>    1. parent rewrite: I have finally figure out a version 1 of it and
> submit it the list. It contain the basic support for '--graph' option
> and I also add a few new test cases for it, also there is a little
> document update;
>    2. the 'git-log -L' basic feature: I have fixed 2 potential bugs
> of it and also try to free the commit_list along with the
> cmd_line_log_walk to try to reduce some memory leak.
>
>    And there is an extra commit, which is a little bug fix of
> previous 'diff-graph' series. :-)
>
>    What's coming on:

In the second half of GSoC, I will try to figure out the following things:
1. Now, when we traverse the line level log, we do:
    limit_list -> sort_in_topologically -> [limit_line_list if
--graph] -> traverse the result.
    It is we deal with the whole history as least 2 times and maybe 3
times when '--graph' given.
    I will try to figure a way to do a 'in place topologically iterate
on the history', to reduce the times of whole history traverse.
2. When we reach the point that, some lines of code are added from
scratch, line movement/copy will be detected, and then follow the
source of movement/copy and go on list the line level log.

That's all, thanks!

-- 
Regards!
Bo
----------------------------
My blog: http://blog.morebits.org
Why Git: http://www.whygitisbetterthanx.com/