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

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

From
Sam Vilain <sam@vilain.net>
Date
Nov 15, 2008, 06:30 UTC
Message-ID
<1226730623.26334.2.camel@maia.lan>
In-Reply-To
<7vr65d7dct.fsf@gitster.siamese.dyndns.org>
On Fri, 2008-11-14 at 21:44 -0800, Junio C Hamano wrote:
> Actually, POSIX does not even talk about EPERM for mkdir(2), but that was
> not my point.  The code does something different from what the proposed
> commit log message talks about.  That was what bothered me.
My wording was a little terse and confusing.  Here's a new one;
Subject: sha1_file.c: resolve confusion EACCESS vs EPERM

EPERM or 'Operation not permitted' is an unlikely error from mkstemp(); test for EACCESS 'Access Denied' instead. Make the special branch which prints the error to the user nicely also understand EACCESS.

Previous: Junio C Hamano
Message 9 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.