All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Zwell <dzwell@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Junio C Hamano <gitster@pobox.com>,
	git@vger.kernel.org, Martin Waitz <tali@admingilde.org>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: git-diff not showing changes (corrupt repo?)
Date: Tue, 02 Oct 2007 23:00:16 -0500	[thread overview]
Message-ID: <470313D0.7020808@gmail.com> (raw)
In-Reply-To: <20071003032331.GA11638@coredump.intra.peff.net>

Jeff King wrote:
 > On Tue, Oct 02, 2007 at 10:17:41PM -0500, Dan Zwell wrote:
 >
 >> 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?
 >

You're absolutely right, my pager was being called and exiting. My 
system configuration must be dodgy, because "echo hi | less 
--quit-if-one-screen" does not display anything unless it in run in 
"screen". But that's not git's fault, and I just need different options, 
for now. Thanks a lot for helping me solve this.

Dan

 >
 > -Peff
 >

  reply	other threads:[~2007-10-03  4:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-02 18:55 git-diff not showing changes (corrupt repo?) Dan Zwell
2007-10-02 19:15 ` Junio C Hamano
2007-10-03  3:17   ` Dan Zwell
2007-10-03  3:23     ` Jeff King
2007-10-03  4:00       ` Dan Zwell [this message]
2007-10-03  4:38         ` Jeff King
2007-10-03  3:44     ` Linus Torvalds
2007-10-02 19:17 ` Jeff King

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=470313D0.7020808@gmail.com \
    --to=dzwell@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=peff@peff.net \
    --cc=tali@admingilde.org \
    --cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.