From: Bo Yang <struggleyb.nku@gmail.com>
To: Git Mailing List <git@vger.kernel.org>
Cc: Thomas Rast <trast@student.ethz.ch>
Subject: [GSoC 2010] The 9nd official week
Date: Sat, 24 Jul 2010 22:48:10 +0800 [thread overview]
Message-ID: <AANLkTi=0gCMfPv1C8kr-KbL2M29XxTHeqcy5L9L2eMOF@mail.gmail.com> (raw)
Hi all,
Here is a short update of my developing status. In the past two
weeks, most of time are spent to revised the posted series. This
includes:
1. Thomas helped me to rewrite all the commit messages to make it
'parsed' well. Thanks a lot for his patience.
2. Fix some issues of the series, this includes most of comments
posted by Junio and some other bugs found by Thomas and myself.
3. Revise the way of parent rewriting. Now, the code has prune most of
uninteresting merges out of the history and can provide a real simple
history of the ranges that user focused on. We will adopt the same way
of parent rewriting as what 'git log path1 path2'. You will see a new
version of this series in next week.
And now, I am working on that show up a combined diff for a merge
commit and a more sensible --full-line-diff ( original
--always-print). :)
That's all, thanks!
--
Regards!
Bo
----------------------------
My blog: http://blog.morebits.org
Why Git: http://www.whygitisbetterthanx.com/
reply other threads:[~2010-07-24 14:48 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='AANLkTi=0gCMfPv1C8kr-KbL2M29XxTHeqcy5L9L2eMOF@mail.gmail.com' \
--to=struggleyb.nku@gmail.com \
--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).