From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: [BUG] The description of pickaxe in git-blame(1) is wrong
Date: Sun, 14 Dec 2008 22:33:48 +0100 [thread overview]
Message-ID: <200812142233.49669.jnareb@gmail.com> (raw)
I think that the description of how 'pickaxe' feature works in
Documentation/git-blame.txt is wrong. It says:
Apart from supporting file annotation, git also supports searching the
development history for when a code snippet occurred in a change. This makes it
possible to track when a code snippet was added to a file, moved or copied
between files, and eventually deleted or replaced. _It works by searching for
a text string in the diff_. A small example:
The part "It works by searching for a text string in the diff" is,
if I remember correctly, wrong. Actually it (I think) compares how
many matches are in pre-image and in post-image, and shows these
commits where those number differ.
This for example means that pickaxe would not pick commit which
moved a fragment from one place to other without change, I think.
--
Jakub Narebski
Poland
reply other threads:[~2008-12-14 21:35 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=200812142233.49669.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.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).