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

Re: [PATCH] sha1_file: make sure correct error is propagated

From
FGFrancis Galiegue <fge@one2team.com>
Date
Nov 14, 2008, 07:44 UTC
Message-ID
<200811140844.58746.fge@one2team.com>
In-Reply-To
<1226647174-15844-1-git-send-email-sam@vilain.net>
Le vendredi 14 novembre 2008, Sam Vilain a écrit :
Show 10 quoted lines
> From: Sam Vilain <samv@maia.lan>
> 
> In the case that a object directory exists, but is not writable, the
> code path that tries to create it is followed and the returned errno
> and path that of the directory tried to be created.  The resultant
> error message is confusing.
> 
> So, if the mkstemp() fails with EPERM, don't try to create the
> directory - return straight away.
> 
Are you sure you didn't mean EACCESS?
-- 
Francis Galiegue
ONE2TEAM
Ingénieur système
Mob : +33 (0) 6 83 87 78 75
Tel : +33 (0) 1 78 94 55 52
fge@one2team.com
40 avenue Raymond Poincaré
75116 Paris
Previous: Sam VilainNext: Sam Vilain
Message 2 of 9 in “sha1_file: make sure correct error is propagated”
  1. sha1_file: make sure correct error is propagatedSam Vilain, Nov 14, 2008
  2. Francis GaliegueNov 14, 2008
  3. Sam VilainNov 14, 2008
  4. Junio C HamanoNov 14, 2008
  5. Francis GaliegueNov 14, 2008
  6. Andreas EricssonNov 14, 2008
  7. Francis GaliegueNov 14, 2008
  8. Junio C HamanoNov 15, 2008
  9. Sam VilainNov 15, 2008

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.