From: "Randall S. Becker" <rsbecker@nexbridge.com>
To: "'Ævar Arnfjörð Bjarmason'" <avarab@gmail.com>, git@vger.kernel.org
Cc: "'Junio C Hamano'" <gitster@pobox.com>,
"'Jeff King'" <peff@peff.net>,
"'Eric Sunshine'" <sunshine@sunshineco.us>,
"'Eric Wong'" <e@80x24.org>,
"'Jakub Narebski'" <jnareb@gmail.com>,
"'Petr Baudis'" <pasky@suse.cz>,
"'Giuseppe Bilotta'" <giuseppe.bilotta@gmail.com>
Subject: RE: [RFC/PATCH] perl: bump the required Perl version to 5.10.0 from 5.8.0
Date: Sat, 23 Dec 2017 12:56:44 -0500 [thread overview]
Message-ID: <000601d37c17$68423da0$38c6b8e0$@nexbridge.com> (raw)
In-Reply-To: <20171223174400.26668-1-avarab@gmail.com>
On December 23, 2017 12:44 PM, Ævar Arnfjörð Bjarmason wrote:
>
> In late 2010 I bumped our perl version dependency from 5.6.* to 5.8.0[1]. Git
> had been failing for a while on <5.8, and it was suspected that nobody cared
> enough to keep using it, which turned out to be true.
>
> Follow that up with bumping the dependency to 5.10.0. The 5.8.0 release
> was released in 2002, and the 5.10.0 release just turned 10 years old[2].
The git HPE NonStop NSE/NSX ports that I maintain has Perl 5.22 generally available, so no objections here. Ours is just a CPAN dependency concern as previously discussed. 😊
Cheers,
Randall
-- Brief whoami: NonStop&UNIX developer since approximately UNIX(421664400)/NonStop(211288444200000000)
-- In my real life, I talk too much.
next prev parent reply other threads:[~2017-12-23 17:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-23 17:44 [RFC/PATCH] perl: bump the required Perl version to 5.10.0 from 5.8.0 Ævar Arnfjörð Bjarmason
2017-12-23 17:56 ` Randall S. Becker [this message]
2017-12-23 23:17 ` brian m. carlson
2017-12-24 11:57 ` Ævar Arnfjörð Bjarmason
2017-12-24 14:38 ` Jeff King
2017-12-24 16:10 ` Ævar Arnfjörð Bjarmason
2017-12-24 23:08 ` Eric Wong
2017-12-25 0:17 ` Ævar Arnfjörð Bjarmason
2017-12-25 1:57 ` Eric Wong
2017-12-27 18:51 ` Junio C Hamano
2017-12-27 19:16 ` Jonathan Nieder
2017-12-27 19:21 ` Jonathan Nieder
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='000601d37c17$68423da0$38c6b8e0$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=avarab@gmail.com \
--cc=e@80x24.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=giuseppe.bilotta@gmail.com \
--cc=jnareb@gmail.com \
--cc=pasky@suse.cz \
--cc=peff@peff.net \
--cc=sunshine@sunshineco.us \
/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).