В Fri, 23 Jan 2015 21:38:59 +0300
Andrei Borzenkov пишет:
> В Sun, 7 Dec 2014 20:34:57 +0300
> Andrei Borzenkov пишет:
>
> > I have two pending patches for gnulib; each one is included upstream.
> > What is the policy in this case - update individual files, add patches
> > to be applied at auto
Thank you. Do you know how big the gnulib update would be?
В Fri, 23 Jan 2015 21:38:59 +0300
Andrei Borzenkov пишет:
> В Sun, 7 Dec 2014 20:34:57 +0300
> Andrei Borzenkov пишет:
>
> > I have two pending patches for gnulib; each one is included upstream.
> > What is the policy in this case - upda
В Thu, 5 Mar 2015 19:23:35 +0100
"Vladimir 'phcoder' Serbinenko" пишет:
> Thank you. Do you know how big the gnulib update would be?
I was reluctant to do full update before 2.02. Even external-inline.m4
contains far more changes than I would prefer in this case.
Here is git diff --shortstat fo
В Thu, 5 Mar 2015 21:47:42 +0300
Andrei Borzenkov пишет:
> В Thu, 5 Mar 2015 19:23:35 +0100
> "Vladimir 'phcoder' Serbinenko" пишет:
>
> > Thank you. Do you know how big the gnulib update would be?
>
> I was reluctant to do full update before 2.02. Even external-inline.m4
> contains far more c
Some installations have several python versions installed. This patch
allows the user to choose which one to use by setting $PYTHON, otherwise it
falls back to 'python'.
Signed-off-by: Jon McCune
Thanks,
-Jon
Author: Jon McCune
autogen.sh: Allow overriding the python to be used by setting
В Thu, 5 Mar 2015 14:27:18 -0800
Jonathan McCune пишет:
> Some installations have several python versions installed. This patch
> allows the user to choose which one to use by setting $PYTHON, otherwise it
> falls back to 'python'.
>
Why is it wrong? What is the problem in this case?
> Signed-
