Re: aliases causing “Permission denied” error in git v1.7
- From
- Алексей Данченков <adanchenkov@gmail.com>
- Date
- Nov 5, 2011, 11:51 UTC
- Message-ID
- <CALUFZ3mgR8aRGO2yCfxKvHXqmz4ZOXBNSPuq0Q69yZ7ys5ttzQ@mail.gmail.com>
- In-Reply-To
- <7vhb2jbopp.fsf@alter.siamese.dyndns.org>
Thank you very much, Jeff and Junio!
Not only I discovered more than one directory mentioned in the $PATH, but missing, but also learned a lot, including the strace tool.
Cheers, Alexei
2011/11/5 Junio C Hamano <gitster@pobox.com>:
Show 15 quoted lines
> Jeff King <peff@peff.net> writes: > > I do not know why my response is not showing up in the list archive, but > the complaint was that "git co" works for him and "sudo git co" does not. > > I suspect that Alexsey will see differences between these: > > $ sh -c 'echo $PATH $HOME' > $ sudo sh -c 'echo $PATH $HOME' > > Most likely, the latter would say /root/bin and /root; if an element in > the $PATH is unreadable, git would say "cannot exec 'git-co': Permission denied". > > >