| commit | 8361e1d4d343a33a60145129dcf8c08ec7de84f2 | |
| author | Jason Riedy <ejr@EECS.Berkeley.EDU> | |
| Sat, 4 Feb 2006 06:50:57 +0000 (3 22:50 -0800) | ||
| committer | Junio C Hamano <junkio@cox.net> | |
| Sat, 4 Feb 2006 07:35:14 +0000 (3 23:35 -0800) | ||
| tree | 674567489bf78638d94d6c7edc0402eea9f6dea4 | treesnapshot (tar.gz zip) |
| parent | 1fda3d557b7c9e19e008c3a3d77f1922341796d7 | commitdiff |
Use sha1_file.c's mkdir-like routine in apply.c.
As far as I can see, create_subdirectories() in apply.c just
duplicates the functionality of safe_create_leading_directories() from
sha1_file.c. The former has a warm, fuzzy const parameter, but that's
not important.
The potential problem with EEXIST and creating directories should
never occur here, but will be removed by future
safe_create_leading_directories() changes. Other uses of EEXIST in
apply.c should be fine barring intentionally malicious behavior.
Signed-off-by: Jason Riedy <ejr@cs.berkeley.edu>
Signed-off-by: Junio C Hamano <junkio@cox.net>
As far as I can see, create_subdirectories() in apply.c just
duplicates the functionality of safe_create_leading_directories() from
sha1_file.c. The former has a warm, fuzzy const parameter, but that's
not important.
The potential problem with EEXIST and creating directories should
never occur here, but will be removed by future
safe_create_leading_directories() changes. Other uses of EEXIST in
apply.c should be fine barring intentionally malicious behavior.
Signed-off-by: Jason Riedy <ejr@cs.berkeley.edu>
Signed-off-by: Junio C Hamano <junkio@cox.net>
| apply.c | diffblobblamehistory |