git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: merlyn@stonehenge.com (Randal L. Schwartz)
To: Ryan Anderson <ryan@michonline.com>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Perl version support (was Re: [PATCH] git-mv is not able to handle big directories)
Date: 23 Nov 2005 06:27:04 -0800	[thread overview]
Message-ID: <86mzjvphhj.fsf_-_@blue.stonehenge.com> (raw)
In-Reply-To: <20051123135604.GB16995@mythryan2.michonline.com>

>>>>> "Ryan" == Ryan Anderson <ryan@michonline.com> writes:

Ryan> For the kernel, requiring 5.8 shouldn't be a big issue. I suspect it's
Ryan> really only the commercial Unixes where requiring 5.8 would be annoying.

Ryan> Randal, is my guess even remotely accurate?

I'd say that 50% of the Perl-using population is at 5.6, with 25% each
at 5.5 and 5.8.  Those on 5.5 are generally unable to upgrade Perl
for corporate reasons.

Targetting Perl 5.6 would assist broad acceptance of git for the
typical commercial end user.  Targetting 5.5 where possible would
ensure practical success for everyone.

However, I have not seen the "target market" of git discussed yet
(I came late to the party), so if support for 5.6 (or 5.5) is not chosen,
it merely limits the market.

If you'd like, I can review all the Perl code with a tool that
determines the minimum Perl version, and provide patches to bring the
code to 5.5 level.  But if it's likely that someone will say "this
is not important to us", I'd rather not waste my time. :)

-- 
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!

  reply	other threads:[~2005-11-23 14:27 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-23  5:41 [PATCH] git-mv is not able to handle big directories Alexander Litvinov
2005-11-23  6:14 ` Junio C Hamano
2005-11-23  6:32   ` Junio C Hamano
2005-11-23  7:55     ` Randal L. Schwartz
2005-11-23  8:37       ` Junio C Hamano
2005-11-23 13:56         ` Ryan Anderson
2005-11-23 14:27           ` Randal L. Schwartz [this message]
2005-11-23 19:47             ` Perl version support Junio C Hamano
2005-11-23 19:59               ` Randal L. Schwartz
2005-11-23 21:56             ` Perl version support (was Re: [PATCH] git-mv is not able to handle big directories) H. Peter Anvin
2005-11-23 22:01               ` Randal L. Schwartz
2005-11-23 22:02               ` Morten Welinder
2005-11-28  1:46             ` Ryan Anderson
2005-11-28  8:49               ` Andreas Ericsson
2005-11-23 18:53           ` [PATCH] git-mv is not able to handle big directories Junio C Hamano
2005-11-23 19:54             ` Ryan Anderson
     [not found]         ` <200511231619.41497.lan@ac-sw.com>
2005-11-23 14:29           ` Randal L. Schwartz
2005-11-23  7:26   ` git-mv is not able to handle directory with one file in it Alexander Litvinov
2005-11-23  7:57     ` Andreas Ericsson
2005-11-23  9:57       ` Alexander Litvinov
2005-11-23 10:21       ` Alexander Litvinov
2005-11-23 11:07         ` Josef Weidendorfer
2005-11-23 14:47     ` Josef Weidendorfer

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=86mzjvphhj.fsf_-_@blue.stonehenge.com \
    --to=merlyn@stonehenge.com \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=ryan@michonline.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).