From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Strange output of git-diff-tree
Date: Wed, 09 Aug 2006 15:24:54 +0200 [thread overview]
Message-ID: <ebcnml$btf$1@sea.gmane.org> (raw)
First (noticed by matled) is that for git-diff-tree with single tree
as an argument it outputs fist commit-id of commit given at input.
It is not mentioned in documentation and I think totally unnecessary:
1038:jnareb@roke:~/git> git diff-tree --abbrev origin
d5dc6a76d49367cddc015e01d2e9aa22e64d7e28
:040000 040000 44fb36d... 1c26294... M Documentation
Second, for some combination of options for it returns "..." instead of
0{40} for file creation. It seems that the culprit is "--find-copies-harder"
option:
1043:jnareb@roke:~/git> git rev-list --full-history next | \
git diff-tree --find-copies-harder -B -C -M -r --full-history --stdin \
-- gitweb/gitweb.perl gitweb/gitweb.cgi gitweb.cgi | less | grep " A"
:000000 100755 ... 017664b8f440f5ec151cf5653245ee02aefd3db2 A gitweb.cgi
1047:jnareb@roke:~/git> git rev-list --full-history next | \
git diff-tree -B -C -M -r --stdin \
-- gitweb/gitweb.perl gitweb/gitweb.cgi gitweb.cgi | less | grep " A"
:000000 100755 0000000000000000000000000000000000000000 017664b8f440f5ec151cf5653245ee02aefd3db2 A gitweb.cgi
Third, while it detects that gitweb/gitweb.perl was renamed from
gitweb/gitweb.cgi:
[...] R100 gitweb/gitweb.cgi gitweb/gitweb.perl
it does not notice that gitweb/gitweb.cgi was gitweb.cgi in
1130ef362fc8d9c3422c23f5d5a833e93d3f5c13.
All those for git version 1.4.1.1
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next reply other threads:[~2006-08-09 13:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-09 13:24 Jakub Narebski [this message]
2006-08-09 18:24 ` Strange output of git-diff-tree Junio C Hamano
2006-08-09 18:28 ` Junio C Hamano
2006-08-09 19:26 ` Junio C Hamano
2006-08-09 19:30 ` (Unsolicited hint) straightening out stray "git bisect" Junio C Hamano
2006-08-09 20:17 ` Strange output of git-diff-tree 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='ebcnml$btf$1@sea.gmane.org' \
--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).