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

Re: [PATCH 1/1] run-command.c: ignore bad permissions on dirs in PATH

From
DRDale Rowley <ddrowley@gmail.com>
Date
May 26, 2010, 02:36 UTC
Message-ID
<4BFC8943.6090504@gmail.com>
In-Reply-To
<4BFB75DD.7030201@viscovery.net>
> That is, when you write a new git command and forget to set execute
> permission, you lose the "Permission denied" error. (Ditto if you
> accidentally remove execute permission from an existing external git command.)

True, but after getting the warning that 'git-frob' doesn't exist, it would probably only take a minute to figure out that 'git-frob' permissions need to be fixed, and then it's understandable why git choked on it. In contrast, it took me a while to discover my PATH permissions problem, and even then it wasn't clear why git should die because of a permissions problem on a directory that had little to do with git.

Dale
Previous: Johannes Sixt
Message 4 of 4 in “run-command.c: ignore bad permissions on dirs in PATH”
  1. 1/1 run-command.c: ignore bad permissions on dirs in PATHDale Rowley, May 25, 2010
  2. Junio C HamanoMay 25, 2010
  3. Johannes SixtMay 25, 2010
  4. Dale RowleyMay 26, 2010

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.