On Thu, Jul 19, 2012 at 06:04:32PM -0400, Bart Baker wrote:
> > Try running `git diff` so that is sees the GIT_TRACE environment
> > variable set to 1, and post the output here.
> $ sudo su
> # export GIT_TRACE=1
> # git diff
> trace: built-in: git 'diff'
> trace: run_command: 'pager'
> trace: exec: 'pager'
> diff --git a/tp_proj.py b/tp_proj.py
> index 3adcb6d..85b98f5 100644
> --- a/tp_proj.py
> +++ b/tp_proj.py
Can you please verify you do have sensible permissions on your work
tree files and the stuff under .git?
Sounds a bit insane, but people repeatedly post questions on SO having
problems after cloning a repo as root (for bizzare reasons) and then
attempting to work with it as a regular user. (Well, Git usually seems
to complain about this loudly but let's pretend your case is special.)
The simplest way to check is to run
$ ls -lR | less
in your work tree and look for something suspicious.
A more elaborate and automated way would be to run
$ find . \! \( -user you -a -group you \) -print
in your work tree with "you" replaced by your user name and primary
group name (or whatever group your project directory is supposed to
have; usually it's the same as your user name).
> > Another question: do you have the PAGER environment variable defined?
> There was not output returned for echo $PAGER
Okay, this means you have a /usr/bin/pager symlink maintained by the
Please now show the results of running the following commands.
$ update-alternatives --display pager
This is just to see what the system thinks your pager is.
$ type pager
# type pager
See if they differ. They shouldn't, but if they do, this would explain
$ echo $PATH
# echo $PATH
Actually, this is only interesting if you and root see different pagers.
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To post to this group, send email to email@example.com.
To unsubscribe from this group, send email to
For more options, visit this group at