From: Junio C Hamano <junkio@cox.net>
To: Petr Baudis <pasky@suse.cz>
Cc: git@vger.kernel.org,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Linus Torvalds <torvalds@osdl.org>,
merlyn@stonehenge.com (Randal L. Schwartz)
Subject: Re: PPC SHA-1 Updates in "pu"
Date: Sun, 25 Jun 2006 03:48:45 -0700 [thread overview]
Message-ID: <7vzmg1v7ci.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20060625102037.GI29364@pasky.or.cz> (Petr Baudis's message of "Sun, 25 Jun 2006 12:20:37 +0200")
Petr Baudis <pasky@suse.cz> writes:
>> And old ones. If you would require me to upgrade to Perl 5.8.1, I would
>> rather stop upgrading git.
>
> please read it again - I'm not requiring you to upgrade to Perl 5.8.1.
> I'm just saying that if you have Perl older than 5.8.1, you might need
> to install some extra modules from CPAN.
>
> Now, if that's not acceptable either that's fine by me and I can
> adapt, I just need to know at which point we _will_ require you to
> upgrade or install extra modules.
I vaguely recall that last time we discussed the minimum Perl
version requirement somebody perhaps Merlyn said 5.6 is old
enough but in some corporate settings people may still be stuck
with 5.004.
Tentatively let's say our cut-off point is somewhere around 5.6.
If we can get away without relying on extra from CPAN that would
be great. Otherwise as long as the modules from CPAN we end up
depending on are all compatible with the cut-off version of Perl
that would be acceptable. We might even try to be nicer and
carry a straight copy of what we require from CPAN in compat/
just like we have subprocess.py there (modulo licensing worries
if any, of course).
Johannes, Linus and the list, would that be a good enough
guideline?
next prev parent reply other threads:[~2006-06-25 10:48 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-23 17:18 x86 asm SHA1 (draft) linux
2006-06-24 0:18 ` Junio C Hamano
2006-06-24 1:22 ` linux
2006-06-24 7:03 ` Junio C Hamano
2006-06-24 7:59 ` From b65bc21e7d8dc8cafc70dfa6354cb66b8874b2d9 Mon Sep 17 00:00:00 2001, [PATCH] Makefile: add framework to verify and bench sha1 implementations Junio C Hamano, Junio C Hamano
2006-06-24 9:29 ` From b65bc21e7d8dc8cafc70dfa6354cb66b8874b2d9 Mon Sep 17 00:00:00 2001 " linux
2006-06-24 19:47 ` Junio C Hamano
2006-06-24 9:20 ` x86 asm SHA1 (draft) linux
2006-06-24 10:03 ` PPC SHA-1 Updates in "pu" Junio C Hamano
2006-06-24 18:55 ` Linus Torvalds
2006-06-24 20:21 ` Junio C Hamano
2006-06-24 20:42 ` Linus Torvalds
2006-06-24 23:59 ` Junio C Hamano
2006-06-25 1:02 ` Petr Baudis
2006-06-25 1:40 ` [PATCH] Git.pm build: Fix quoting and missing GIT-CFLAGS dependency Petr Baudis
2006-06-25 3:03 ` Junio C Hamano
2006-06-25 15:21 ` Petr Baudis
2006-06-26 6:48 ` Junio C Hamano
2006-07-01 23:59 ` [POOL] Who likes running Git without make install? Petr Baudis
2006-07-02 0:05 ` Junio C Hamano
2006-07-02 0:08 ` Junio C Hamano
2006-07-02 11:30 ` Petr Baudis
2006-07-02 17:19 ` Junio C Hamano
2006-07-03 6:54 ` [POLL] " Junio C Hamano
2006-07-03 7:58 ` Petr Baudis
2006-07-03 8:08 ` Junio C Hamano
2006-07-03 8:17 ` Petr Baudis
2006-07-03 8:37 ` Johannes Schindelin
2006-06-25 1:24 ` PPC SHA-1 Updates in "pu" Petr Baudis
2006-06-25 3:57 ` Junio C Hamano
2006-06-25 9:34 ` Petr Baudis
2006-06-25 10:07 ` Johannes Schindelin
2006-06-25 10:20 ` Petr Baudis
2006-06-25 10:48 ` Junio C Hamano [this message]
2006-06-25 13:44 ` Johannes Schindelin
2006-06-25 18:46 ` Randal L. Schwartz
2006-06-25 23:23 ` Johannes Schindelin
2006-06-26 1:51 ` perl profiling (was: PPC SHA-1 Updates in "pu") Jeff King
2006-06-26 6:49 ` PPC SHA-1 Updates in "pu" Junio C Hamano
2006-06-30 1:28 ` GIt.xs merge status Junio C Hamano
2006-06-30 5:08 ` Pavel Roskin
2006-06-30 7:18 ` Git.xs " Junio C Hamano
2006-06-30 7:28 ` Pavel Roskin
2006-06-30 9:53 ` GIt.xs " Johannes Schindelin
2006-06-30 10:26 ` Junio C Hamano
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=7vzmg1v7ci.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=merlyn@stonehenge.com \
--cc=pasky@suse.cz \
--cc=torvalds@osdl.org \
/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).