Re: blame -M vs. log -p|grep -c ^+ weirdness
- From
Thomas Rast <trast@student.ethz.ch>
- Date
- Aug 11, 2009, 11:56 UTC
- Message-ID
- <200908111356.06558.trast@student.ethz.ch>
- In-Reply-To
- <200908111216.05131.trast@student.ethz.ch>
Thomas Rast wrote:
> git://csa.inf.ethz.ch/domjudge-public.git
Turns out this is locked down from the outside as of this writing, so I mirrored it at
git://thomasrast.ch/domjudge.git
> git ls-files | while read f; do git blame -M -- "$f"; done |
[...]
> git log --no-merges -p upstream/2.2.. | grep '^+' | grep -v -c '^+++'
[...]
> Björn Steinbrink suggested on IRC that I use -M5 -C5 -C5 -C5, which > indeed reduces it to
As Björn kindly pointed out once he had access to the repo, the blame -M works for binary files too, while log -p doesn't; and 'bin/sh-static' and 'doc/logos/DOMjudgelogo.pdf' live under other names in the upstream repository too, so sufficiently many -C blame them on upstream instead. So that resolves the mystery.
--
Thomas Rast
trast@{inf,student}.ethz.ch