From: Brandon Casey <drafnel@gmail.com>
To: git@vger.kernel.org
Cc: pw@padd.com, esr@thyrsus.com, john@keeping.me.uk,
Brandon Casey <drafnel@gmail.com>
Subject: [PATCH 0/2] git-p4 support for older python
Date: Fri, 25 Jan 2013 12:43:59 -0800 [thread overview]
Message-ID: <1359146641-27810-1-git-send-email-drafnel@gmail.com> (raw)
Offered for consideration.
These two patches allow git-p4 to run on python 2.4 which is shipped on
RHEL 5.X. The changes are minor and unintrusive in my opinion, but please
feel free to reject one or both of them for any reason (in which case the
version check at the top of git-p4.py should be updated).
Brandon Casey (2):
git-p4.py: support Python 2.5
git-p4.py: support Python 2.4
INSTALL | 2 +-
git-p4.py | 30 ++++++++++++++++++++++++++----
t/t9802-git-p4-filetype.sh | 11 ++++++-----
3 files changed, 33 insertions(+), 10 deletions(-)
--
1.8.1.1.297.gad3d74e
-----------------------------------------------------------------------------------
This email message is for the sole use of the intended recipient(s) and may contain
confidential information. Any unauthorized review, use, disclosure or distribution
is prohibited. If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.
-----------------------------------------------------------------------------------
next reply other threads:[~2013-01-25 20:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-25 20:43 Brandon Casey [this message]
2013-01-25 20:44 ` [PATCH 1/2] git-p4.py: support Python 2.5 Brandon Casey
2013-01-26 12:45 ` Pete Wyckoff
2013-01-26 18:19 ` Brandon Casey
2013-01-25 20:44 ` [PATCH 2/2] git-p4.py: support Python 2.4 Brandon Casey
2013-01-26 12:48 ` Pete Wyckoff
2013-01-26 19:02 ` Brandon Casey
2013-01-25 21:10 ` [PATCH 0/2] git-p4 support for older python Junio C Hamano
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=1359146641-27810-1-git-send-email-drafnel@gmail.com \
--to=drafnel@gmail.com \
--cc=esr@thyrsus.com \
--cc=git@vger.kernel.org \
--cc=john@keeping.me.uk \
--cc=pw@padd.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).