All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Eric Wong <e@80x24.org>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
	"Jeff King" <peff@peff.net>,
	git@vger.kernel.org, "Eric Sunshine" <sunshine@sunshineco.com>,
	"Jakub Narebski" <jnareb@gmail.com>,
	"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: Wed, 27 Dec 2017 10:51:15 -0800	[thread overview]
Message-ID: <xmqqzi64m2cc.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20171225015744.o47ackbwi2wbtkbv@untitled> (Eric Wong's message of "Mon, 25 Dec 2017 01:57:44 +0000")

Eric Wong <e@80x24.org> writes:

> Fair enough, I haven't run 5.8 in a while, either.  One concern
> I have is it makes reviewing more difficult as the language gets
> bigger and (even more) unfamiliar constructs pop up.  This is
> probably more important for git as most of us are not dedicated
> Perl hackers.

Yes, but that cuts both ways.  When we do get a less amateur Perl
folks who contribute and review, they are more and more likely to be
fluent in modern versions of Perl than the ancient ones some of us
who learned the tongue long time ago are familiar with.  Telling
them to limit themselves to what is also available in ancient
versions is a burden that is backwards.

So

> What mostly bugs me about this is going from:
>
> 	"we'll accept patches to keep your old system working"
>
>  to:
>
> 	"your software is too old, upgrade or go away"

is something we need to be able to say at some point.

  reply	other threads:[~2017-12-27 18:51 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
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 [this message]
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=xmqqzi64m2cc.fsf@gitster.mtv.corp.google.com \
    --to=gitster@pobox.com \
    --cc=avarab@gmail.com \
    --cc=e@80x24.org \
    --cc=git@vger.kernel.org \
    --cc=giuseppe.bilotta@gmail.com \
    --cc=jnareb@gmail.com \
    --cc=peff@peff.net \
    --cc=sunshine@sunshineco.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 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.