Jeff King <peff@xxxxxxxx> writes: > On Tue, Jun 04, 2013 at 12:10:25PM -0700, Jonathan Nieder wrote: > >> >> However, since changing user id and leaving $HOME is so common, there is >> >> a patch under consideration to loosen the check only for the case of >> >> EACCES on files in $HOME. That commit is 4698c8f (config: allow >> >> inaccessible configuration under $HOME, 2013-04-12); it's not yet in any >> >> released version of git, though. >> [...] >> > I've a PHP script in ~/public_html that runs git. Without the mentioned >> > patch, the script bails out due to this error. This time it's Apache >> > that gets me into trouble because at the time the PHP script and git >> > run, $HOME is still /root, but the user identity is not root anymore. >> > The patch is direly needed; without it, I need to use 'env >> > HOME=/home/j6t /usr/local/bin/git' in my script. >> >> I could be remembering wrong, but I thought it was not so much "under >> consideration" as "accepted for 1.8.4". I haven't heard any >> compelling reasons not to apply it. >> >> Would it would make sense against earlier releases as well? > > Yeah, I think it would. I only said "under consideration" because I saw > that it was in "next" and not elsewhere, and did not hunt down the exact > status in "What's Cooking". Sorry about that; it is in 'master' but "What's cooking" for that pushout hasn't been published yet (the description of what I did yesterday will be rolled into today's issue together with the description of what I did today at the end of day). -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html