From: Bo Yang <struggleyb.nku@gmail.com>
To: Git Mailing List <git@vger.kernel.org>
Cc: Jens Lehmann <Jens.Lehmann@web.de>, Thomas Rast <trast@student.ethz.ch>
Subject: Re: [GSoC Update] The 7th week
Date: Sun, 11 Jul 2010 15:02:38 +0800 [thread overview]
Message-ID: <AANLkTilejGRx_ypUExeXvr04oI5voHSWV-WlAEbTmPu1@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimyVewBItArmb7Q2ELy0Dk20LvxIdhoucap8nO6@mail.gmail.com>
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/
prev parent reply other threads:[~2010-07-11 7:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-11 6:57 [GSoC Update] The 7th week Bo Yang
2010-07-11 7:02 ` Bo Yang [this message]
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=AANLkTilejGRx_ypUExeXvr04oI5voHSWV-WlAEbTmPu1@mail.gmail.com \
--to=struggleyb.nku@gmail.com \
--cc=Jens.Lehmann@web.de \
--cc=git@vger.kernel.org \
--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).