From: Jakub Narebski <jnareb@gmail.com>
To: Jay Soffian <jaysoffian@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
Michael Witten <mfwitten@gmail.com>, git <git@vger.kernel.org>
Subject: Re: Oldest supported Perl version
Date: Mon, 20 Apr 2009 10:59:14 -0700 (PDT) [thread overview]
Message-ID: <m3eivnp5p4.fsf@localhost.localdomain> (raw)
In-Reply-To: <76718490904200759l24e1bd9exe0e1b60f7b2847a7@mail.gmail.com>
Jay Soffian <jaysoffian@gmail.com> writes:
> On Sun, Apr 19, 2009 at 9:58 PM, Junio C Hamano <gitster@pobox.com> wrote:
> >
> > Now the real question was if we still support anything older, and if so
> > what is the bottom version?
> >
> > I certainly can go with "5.8.1 or later", but I vaguely recall during the
> > gitweb discussion we said anything without the utf-8 support is unusable
> > for gitweb, but I think we also said that the rest of the git codebase
> > should support running with something older (5.6.1, perhaps).
> So here's my take-away. For the *.perl scripts and gitweb, it's
> 5.8.0. For the test suite and Git.pm, all Perl versions are
> theoretically supported, but for practical purposes, it may be
> 5.6.0.
Errr... no. For gitweb we require good Unicode support, which means
Perl 5.8.x (IIRC 5.8.1). For all other: commands (and helpers)
written in Perl like git-svn, fragments of Perl in test suite (because
of incompatibility and corner cases of shell scripting) - with possible
exception of testing gitweb, and Git.pm (which some commands in Perl
use) I think it is reasonable to expect 5.6.0 at least.
> Whatever is decided this time, perhaps it should be burned into the tops of
> the *.perl scripts (i.e. "require 5.008;"). It should also be added to
> CodingGuidelines. You know, so this conversation doesn't keep recurring. :-)
>
> j.
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2009-04-20 18:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-20 14:59 Oldest supported Perl version Jay Soffian
2009-04-20 15:40 ` [PATCH RFC3.5 04/12] send-email: Verification for --smtp-server and --smpt-server-port Michael Witten
2009-04-20 15:43 ` Oldest supported Perl version Michael Witten
2009-04-20 15:51 ` Jay Soffian
2009-04-20 16:18 ` H.Merijn Brand
2009-04-20 17:29 ` Johannes Schindelin
2009-04-20 21:07 ` H.Merijn Brand
2009-04-20 17:59 ` Jakub Narebski [this message]
2009-04-20 18:27 ` Jay Soffian
2009-04-20 18:32 ` Jay Soffian
2009-04-20 18:40 ` Michael Witten
2009-04-20 19:11 ` Johannes Schindelin
2009-04-20 19:58 ` Michael Witten
2009-04-20 21:10 ` H.Merijn Brand
2009-04-20 22:38 ` Michael Witten
2009-04-20 22:39 ` Michael Witten
2009-04-20 22:56 ` H.Merijn Brand
2009-04-21 3:08 ` Jeff King
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=m3eivnp5p4.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jaysoffian@gmail.com \
--cc=mfwitten@gmail.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).