From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: "Shawn O. Pearce" <spearce@spearce.org>, git@vger.kernel.org
Subject: Re: git log --numstat disagrees with git apply --numstat
Date: Mon, 15 Dec 2008 01:57:07 -0800 [thread overview]
Message-ID: <7vhc55yd58.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20081212022156.GC23128@sigill.intra.peff.net> (Jeff King's message of "Thu, 11 Dec 2008 21:21:56 -0500")
Jeff King <peff@peff.net> writes:
> BTW, I got a little confused looking at the parameters to xdi_diff_outf,
> since ecb gets passed in full of random garbage. I don't know if this
> cleanup is worth applying:
I think this makes sense, but let's do this after 1.6.1 final. It does
not fix anything, and I'd rather avoid distraction.
next prev parent reply other threads:[~2008-12-15 9:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-11 23:53 git log --numstat disagrees with git apply --numstat Shawn O. Pearce
2008-12-12 1:52 ` Jeff King
2008-12-12 2:08 ` Jeff King
2008-12-12 2:21 ` Jeff King
2008-12-15 9:57 ` Junio C Hamano [this message]
2008-12-15 20:32 ` Jeff King
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=7vhc55yd58.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=spearce@spearce.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).