From: Junio C Hamano <gitster@pobox.com>
To: John Keeping <john@keeping.me.uk>
Cc: git@vger.kernel.org, Brandon Casey <drafnel@gmail.com>
Subject: Re: What's cooking in git.git (Jan 2013, #11; Wed, 30)
Date: Wed, 30 Jan 2013 11:17:15 -0800 [thread overview]
Message-ID: <7v4nhylbus.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <20130130190759.GJ1342@serenity.lan> (John Keeping's message of "Wed, 30 Jan 2013 19:07:59 +0000")
John Keeping <john@keeping.me.uk> writes:
> On Wed, Jan 30, 2013 at 10:33:10AM -0800, Junio C Hamano wrote:
>> [Discarded]
>>
>> * jk/update-install-for-p4 (2013-01-20) 1 commit
>> . INSTALL: git-p4 doesn't support Python 3
>>
>> Made obsolete by bc/git-p4-for-python-2.4 topic.
>
> I disagree with this - that branch doesn't change INSTALL to list "not
> Python 3" in the supported versions.
>
> Brandon, would you mind doing s/2.4 or later/2.4 - 2.7/ on your branch?
Thanks for being a careful reader.
Let's do something like this on top of the topic.
INSTALL | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/INSTALL b/INSTALL
index b96e16d..2dc3b61 100644
--- a/INSTALL
+++ b/INSTALL
@@ -131,8 +131,9 @@ Issues of note:
use English. Under autoconf the configure script will do this
automatically if it can't find libintl on the system.
- - Python version 2.4 or later is needed to use the git-p4
- interface to Perforce.
+ - Python version 2.4 or later (but not 3.x, which is not
+ supported by Perforce) is needed to use the git-p4 interface
+ to Perforce.
- Some platform specific issues are dealt with Makefile rules,
but depending on your specific installation, you may not
next prev parent reply other threads:[~2013-01-30 19:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-30 18:33 What's cooking in git.git (Jan 2013, #11; Wed, 30) Junio C Hamano
2013-01-30 19:07 ` John Keeping
2013-01-30 19:17 ` Junio C Hamano [this message]
2013-01-30 19:19 ` John Keeping
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=7v4nhylbus.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=drafnel@gmail.com \
--cc=git@vger.kernel.org \
--cc=john@keeping.me.uk \
/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.