From: Jonathan Nieder <jrnieder@gmail.com>
To: Johannes Sixt <j6t@kdbg.org>
Cc: Jeff King <peff@peff.net>, Ian Kumlien <pomac@vapor.com>,
git@vger.kernel.org
Subject: Re: git-daemon: needs /root/.config/git/config?
Date: Tue, 4 Jun 2013 12:10:25 -0700 [thread overview]
Message-ID: <20130604191025.GG28153@google.com> (raw)
In-Reply-To: <51AE3A88.2080203@kdbg.org>
Johannes Sixt wrote:
> Am 04.06.2013 18:08, schrieb Jeff King:
>> 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?
Thanks,
Jonathan
next prev parent reply other threads:[~2013-06-04 19:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-04 14:13 git-daemon: needs /root/.config/git/config? Ian Kumlien
2013-06-04 16:08 ` Jeff King
2013-06-04 19:05 ` Johannes Sixt
2013-06-04 19:10 ` Jonathan Nieder [this message]
2013-06-04 19:20 ` Junio C Hamano
2013-06-04 21:06 ` Jeff King
2013-06-04 21:24 ` Junio C Hamano
2013-06-05 11:19 ` Ian Kumlien
2013-06-05 11:43 ` Andreas Krey
2013-06-05 15:43 ` Jeff King
2013-06-09 12:47 ` Bernhard R. Link
2013-06-10 12:06 ` Ian Kumlien
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130604191025.GG28153@google.com \
--to=jrnieder@gmail.com \
--cc=git@vger.kernel.org \
--cc=j6t@kdbg.org \
--cc=peff@peff.net \
--cc=pomac@vapor.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.