From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Cc: "Robert Schiele" <rschiele@gmail.com>,
"Ask Bjørn Hansen" <ask@develooper.com>
Subject: Re: [PATCH] change Perl syntax to support Perl 5.6
Date: Sun, 31 Aug 2008 18:48:10 -0700 [thread overview]
Message-ID: <7vhc901vs5.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <7vljyc1wzg.fsf@gitster.siamese.dyndns.org> (Junio C. Hamano's message of "Sun, 31 Aug 2008 18:22:11 -0700")
Junio C Hamano <gitster@pobox.com> writes:
> Ask Bjørn Hansen <ask@develooper.com> writes:
> ...
>>> This is an alternative to my previous patch that just declared Perl
>>> 5.8 to
>>> be the required version.
>>
>> +1 to that one.
>
> Now, would somebody volunteer to go everywhere our user base (who no
> longer read Release Notes) hang around, post a message saying that some
> people on git development list are proposing to drop Perl 5.6 support, and
> if the proposal goes ahead, it is possible that the next release may force
> upgrading Perl for them, to make sure they won't complain saying they've
> never heard about the "incompatible change" beforehand?
Just in case before anybody overreacts without reading the mailing list
backlog; the above is meant to be a moderately bitter joke ;-)
I tend to think that everybody who needs to run git in their development
environment (the deployment site could be running with ancient Perl for
all we care --- after all, git or any SCM is primarily to be run in the
development environment, and even if people use git to transfer the end
result from the development side, all they need is the really core part of
history tranfer tools like fetch, push and checkout on the deployed site;
these tools do not depend on Perl) would be running 5.8 by now. Granted,
some development machine need to have the exact same version of everything
as the intended deployment environment for testing purposes, and some
people may be developing a piece of software that is meant to run on Perl
that is no more recent than 5.6, but with virtual machines and all, I
think it would be rare to have such a setup --- it is a lot easier to
develop on a platform with more reasonably recent Perl that your
development tools (not limited to git itself) may depend on, and test on a
virtual bochs with an ancient software configuration as the intended
deployment site.
So I personally think it is probably Ok to declare that we do depend on
5.8.
prev parent reply other threads:[~2008-09-01 1:49 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-30 17:39 [PATCH] change Perl syntax to support Perl 5.6 Robert Schiele
2008-08-30 18:00 ` Jeff King
2008-08-30 18:06 ` Junio C Hamano
2008-08-30 18:13 ` Jeff King
2008-08-30 18:34 ` Robert Schiele
2008-08-30 18:39 ` Jeff King
2008-08-30 20:37 ` Jakub Narebski
2008-08-30 21:21 ` Robert Schiele
2008-08-31 5:35 ` Avery Pennarun
2008-08-31 13:37 ` Randal L. Schwartz
2008-08-31 16:27 ` Junio C Hamano
2008-08-31 18:29 ` Avery Pennarun
2008-08-31 20:23 ` Jakub Narebski
2008-08-31 20:34 ` Petr Baudis
2008-09-01 3:57 ` H. Peter Anvin
2008-09-01 4:22 ` Robert Schiele
2008-09-01 13:06 ` Tom G. Christensen
2008-09-04 17:28 ` Brandon Casey
2008-09-05 6:34 ` Tom G. Christensen
2008-08-31 20:55 ` Jakub Narebski
2008-09-01 1:52 ` Jay Soffian
2008-09-01 21:42 ` Alex Riesen
2008-09-02 0:23 ` Avery Pennarun
2008-09-02 17:50 ` Avery Pennarun
2008-08-30 20:20 ` Junio C Hamano
2008-08-31 13:35 ` Randal L. Schwartz
2008-08-31 19:54 ` Ask Bjørn Hansen
2008-09-01 1:22 ` Junio C Hamano
2008-09-01 1:48 ` Junio C Hamano [this message]
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=7vhc901vs5.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=ask@develooper.com \
--cc=git@vger.kernel.org \
--cc=rschiele@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).