From: pi song <pi.songs@gmail.com>
To: Miklos Vajna <vmiklos@frugalware.org>,
git@vger.kernel.org, gitster@pobox.com
Cc: rene.scharfe@lsrfire.ath.cx
Subject: Re: [PATCH2/2] Libify blame
Date: Tue, 17 Mar 2009 10:11:05 +1100 [thread overview]
Message-ID: <1b29507a0903161611w735d3ed2l958eeec9295c7432@mail.gmail.com> (raw)
In-Reply-To: <20090316200418.GM3817@genesis.frugalware.org>
This was generated from git format-patch -M. After applying the patch,
you can look in git gui to confirm that I didn't change any logic.
Pi Song
On Tue, Mar 17, 2009 at 7:04 AM, Miklos Vajna <vmiklos@frugalware.org> wrote:
> On Mon, Mar 16, 2009 at 02:49:31PM +0100, Sverre Rabbelier <srabbelier@gmail.com> wrote:
>> 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.
>
> Or just use git format-patch -M?
>
next prev parent reply other threads:[~2009-03-16 23:12 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
2009-03-16 20:04 ` Miklos Vajna
2009-03-16 23:11 ` pi song [this message]
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=1b29507a0903161611w735d3ed2l958eeec9295c7432@mail.gmail.com \
--to=pi.songs@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=rene.scharfe@lsrfire.ath.cx \
--cc=vmiklos@frugalware.org \
/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).