git/list[1] front-page[2] threads[3] people[4] search[5] about
 

aliases causing “Permission denied” error in git v1.7

From
АДАлексей Данченков <adanchenkov@gmail.com>
Date
Nov 4, 2011, 08:09 UTC
Message-ID
<CALUFZ3n9cpHw3r3rcGriDqvJ+UM83L3Q19m=0YeAy51LBJzosA@mail.gmail.com>
Hi!

$ git co -b newbranch $ git co oldbranch

results in "fatal: cannot exec 'git-co': Permission denied" error.
In the same time, things like

$ git checkout -b newbranch $ git checkout oldbranch

and

$ sudo git co -b newbranch $ sudo git co oldbranch

work as expected. Ownership rights for the .git die are set for the user and 0755/0644 are the mode for .git dir/subdir/files. There are no git-co script anywhere in the system (as it is an alias to git-checkout, which resides in /usr/libexec/git-core).

Aliases are defined in .gitconfig of the home dir:

[alias] co = checkout

There is no difference in git config for root or normal user.

Things work well as expected when I install git v1.6. Going back to 1.7 gives me the same error.

What am I missing?
---
Gentoo / kernel v3.0.6 / git v1.7.3.4
Next: Jeff King
Message 1 of 3 in “aliases causing “Permission denied” error in git v1.7”
  1. Алексей ДанченковNov 4, 2011
  2. Jeff KingNov 4, 2011
  3. Алексей ДанченковNov 5, 2011

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.