sha1_file.c: resolve confusion EACCES vs EPERM
An earlier commit 916d081
(Nicer error messages in case saving an object
to db goes wrong, 2006-11-09) confused EACCES with EPERM, the latter of
which is an unlikely error from mkstemp().
Signed-off-by: Sam Vilain <sam@vilain.net>
This commit is contained in:
parent
65117abc04
commit
35243577ab
@ -2246,7 +2246,7 @@ static int write_loose_object(const unsigned char *sha1, char *hdr, int hdrlen,
|
||||
filename = sha1_file_name(sha1);
|
||||
fd = create_tmpfile(tmpfile, sizeof(tmpfile), filename);
|
||||
if (fd < 0) {
|
||||
if (errno == EPERM)
|
||||
if (errno == EACCES)
|
||||
return error("insufficient permission for adding an object to repository database %s\n", get_object_directory());
|
||||
else
|
||||
return error("unable to create temporary sha1 filename %s: %s\n", tmpfile, strerror(errno));
|
||||
|
Loading…
Reference in New Issue
Block a user