From: Sverre Rabbelier <srabbelier@gmail.com>
To: pi song <pi.songs@gmail.com>
Cc: git@vger.kernel.org, gitster@pobox.com, rene.scharfe@lsrfire.ath.cx
Subject: Re: [PATCH2/2] Libify blame
Date: Mon, 16 Mar 2009 14:49:31 +0100 [thread overview]
Message-ID: <fabb9a1e0903160649o6b576976jeb884e18713c154e@mail.gmail.com> (raw)
In-Reply-To: <49BE5466.5050202@gmail.com>
Heya,
On Mon, Mar 16, 2009 at 14:30, pi song <pi.songs@gmail.com> wrote:
> This looks like a very HUGE patch but it does merely splitting the current builtin-blame.c into smaller blame.c without changing any logic.
> This is still WIP. The next patch will organize functions more appropriately.
It would be nice if you could paste the output of "git diff -M" after
the triple-dash to show that it is indeed only a small change.
--
Cheers,
Sverre Rabbelier
next prev parent reply other threads:[~2009-03-16 13:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-16 13:30 [PATCH2/2] Libify blame pi song
2009-03-16 13:49 ` Sverre Rabbelier [this message]
2009-03-16 20:04 ` Miklos Vajna
2009-03-16 23:11 ` pi song
2009-03-17 0:48 ` Junio C Hamano
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=fabb9a1e0903160649o6b576976jeb884e18713c154e@mail.gmail.com \
--to=srabbelier@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pi.songs@gmail.com \
--cc=rene.scharfe@lsrfire.ath.cx \
/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).