Thanks for the suggestion. I had actually commented that out because I
was receiving the same "permission denied" error even though I chmod-ed
the log file to 777. I have meaning to play around with it but haven't
gotten to it. The strace command was suggested by a co-worker but I have
never used it before.
On 05/10/11 06:26, Konstantin Khomoutov wrote:
On Mon, 9 May 2011 20:04:07 -0700 (PDT)
Blu Dragon<[email protected]> wrote:
[...]
#strace git push -v $remote $branch 2&> /var/log/strace-git.log
git push -v $remote $branch
done
exit 0
I wonder if strace'ing yields something of interest?
But for this to work you most probably pass the "-f" command-line
option to strace so that it also traces forked processes--Git is
modular and so it's quite possible that git-push runs a bunch of other
binaries when it does its job.
Hence I'd write it like this:
strace -f -o /tmp/git-strace.log git push -v "$remote" "$branch"
__________ Information from ESET Smart Security, version of virus signature
database 6110 (20110510) __________
The message was checked by ESET Smart Security.
http://www.eset.com
__________ Information from ESET Smart Security, version of virus signature
database 6110 (20110510) __________
The message was checked by ESET Smart Security.
http://www.eset.com
--
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 protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/git-users?hl=en.