{"thread":{"id":"58969","subject":"[Possible Bug] config --system fails when ./etc does not exist","startedAt":"2022-12-17T01:31:20Z","lastAt":"2022-12-17T01:31:20Z","messageCount":1,"participants":["rsbecker@nexbridge.com"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"469200","messageId":"007a01d911b7$4125bd60$c3713820$@nexbridge.com","threadId":"58969","inReplyTo":null,"subject":"[Possible Bug] config --system fails when ./etc does not exist","fromName":"","fromEmail":"rsbecker@nexbridge.com","sentAt":"2022-12-17T01:31:09Z","receivedAt":"2022-12-17T01:31:20Z","isPatch":false,"sender":{"key":"randall.becker@nexbridge.ca","avatar":"https://avatars.githubusercontent.com/u/28956764?v=4"},"body":"On an initial install, the ./etc directory does not exist where git is\ninstalled. This causes git config --system to fail because the ./etc/config\nfile cannot be created because of ENOENT. Is this deliberately intended for\na specific security concern or would a patch to automatically create ./etc\nif it the directory does not exist be desired? It would need a\nstat(\"./etc\".) call prior to attempting to create the ./etc/config file,\nwith appropriate knobs, of course. If the build assumes the use of /etc\ninstead of ./etc inside /usr/local, we probably do not want to do this.\n\nCuriously,\nRandall\n\n"}]}