git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: [GSoC 2010] The 6th week
Date: Fri, 2 Jul 2010 23:05:17 +0800	[thread overview]
Message-ID: <AANLkTilnO-F3Lnu9mdS9bIUXfvdU0C-cnNC170wE2-yB@mail.gmail.com> (raw)

Hi,

    A quick update of status.

1. The patch series has pass one round of modification, this include:
     1) The parsing method is changed from a two-pass way to a one-pass way;
     2) A simple code refactoring get done on 'parse_loc' which is
used by both line.c and builtin/blame.c
2. parent rewriting of line level history traversal
    To compose the basic code structure of this and complete part of
the code. You will see it in next week. :)

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

                 reply	other threads:[~2010-07-02 15:10 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=AANLkTilnO-F3Lnu9mdS9bIUXfvdU0C-cnNC170wE2-yB@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).