Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Ehsan Akhgari <ehsan@mozilla.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] INSTALL: Add docs on how to use custom Python paths.
Date: Mon, 31 Aug 2015 07:53:59 -0700	[thread overview]
Message-ID: <xmqqr3mjy0e0.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <1441027358-27245-1-git-send-email-ehsan@mozilla.com> (Ehsan Akhgari's message of "Mon, 31 Aug 2015 09:22:38 -0400")

Ehsan Akhgari <ehsan@mozilla.com> writes:

> Signed-off-by: Ehsan Akhgari <ehsan@mozilla.com>
> ---
>  INSTALL | 5 +++++
>  1 file changed, 5 insertions(+)
>
> diff --git a/INSTALL b/INSTALL
> index ffb071e..5b7fe91 100644
> --- a/INSTALL
> +++ b/INSTALL
> @@ -148,6 +148,11 @@ Issues of note:
>  	  supported by Perforce) is needed to use the git-p4 interface
>  	  to Perforce.
>  
> +	  By default, git looks for Python installed in /usr/bin/python.
> +	  On systems with a different Python installation path, pass the
> +	  --with-python argument to configure, or set the PYTHON_PATH
> +	  environment variable when using make to build.
> +
>   - Some platform specific issues are dealt with Makefile rules,
>     but depending on your specific installation, you may not
>     have all the libraries/tools needed, or you may have

Thanks for a patch, but I doubt that it is a good idea to do this.

The paragraph we see in the post-context of your patch is meant to
cover it, together with 47 other platform specific locations like
SHELL_PATH, PERL_PATH, CURLDIR, etc.

      parent reply	other threads:[~2015-08-31 14:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-31 13:22 [PATCH] INSTALL: Add docs on how to use custom Python paths Ehsan Akhgari
2015-08-31 14:28 ` Luke Diamand
2015-08-31 14:53 ` Junio C Hamano [this message]

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=xmqqr3mjy0e0.fsf@gitster.mtv.corp.google.com \
    --to=gitster@pobox.com \
    --cc=ehsan@mozilla.com \
    --cc=git@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox