Re: git-diff not showing changes (corrupt repo?)
- From
Jeff King <peff@peff.net>
- Date
- Oct 3, 2007, 03:23 UTC
- Message-ID
- <20071003032331.GA11638@coredump.intra.peff.net>
- In-Reply-To
- <470309D5.702@gmail.com>
On Tue, Oct 02, 2007 at 10:17:41PM -0500, Dan Zwell wrote:
Show 6 quoted lines
> e88ee2915493213ea0d0be64c542c090fefd4b33 is first bad commit > commit e88ee2915493213ea0d0be64c542c090fefd4b33 > Author: Martin Waitz <tali@admingilde.org> > Date: Tue Oct 10 21:16:25 2006 +0200 > > paginate git-diff by default
The only thing this patch does is run the pager, so presumably git-diff _is_ generating output, but calling the pager is broken for some reason. What is the value of $GIT_PAGER and $PAGER on the broken and working machines? Can you confirm that the pager works on both machines?
Show 5 quoted lines
> I discovered this problem on my 64 bit machine, but the problem does not > occur on my 32 bit machine. That is not the only difference between the two > computers, but it seems the most obvious culprit. The 64 bit machine may > have different libraries than the other, as they are running different > distros.
I couldn't reproduce on my 32-bit or 64-bit machine (the former running Debian unstable, the latter Debian stable). But given the patch you bisected to, I think it is more likely that your pager is broken on the 64-bit machine.
-Peff