From: Eckhard Maass <eckhard.maass@gmx.net>
To: git@vger.kernel.org
Cc: Jeff King <peff@peff.net>
Subject: Re: -B option of git log
Date: Fri, 22 Feb 2013 11:14:36 +0100 [thread overview]
Message-ID: <5127450C.5040908@gmx.net> (raw)
In-Reply-To: <20130222005704.GA24287@sigill.intra.peff.net>
On 02/22/2013 01:57 AM, Jeff King wrote:
> I think the problem is that your test file is so tiny that it falls
> afoul of git's MINIMUM_BREAK_SIZE heuristic of 400 bytes (which prevents
> false positives on tiny files). Try replacing your "Lorem ipsum" echo
> with something like "seq 1 150", and I think you will find the result
> you are expecting.
Thanks. Two points, though:
With bigger files, I do get something like:
| M100 d
| R100 d e
The rename is fine. But I am a bit puzzled mit the M - I, somehow,
would have expected an A for add and not a M.
Secondly, would it be a good idea to enhance the documentation on
that point to clarify this minimum size?
SEcki
prev parent reply other threads:[~2013-02-22 10:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-22 0:44 -B option of git log Eckhard Maass
2013-02-22 0:57 ` Jeff King
2013-02-22 10:14 ` Eckhard Maass [this message]
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=5127450C.5040908@gmx.net \
--to=eckhard.maass@gmx.net \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).