From: "Rafael Garcia-Suarez" <rgarciasuarez@gmail.com>
To: "Petr Baudis" <pasky@suse.cz>
Cc: "Lea Wiemann" <lewiemann@gmail.com>,
"Jakub Narebski" <jnareb@gmail.com>,
git@vger.kernel.org, "John Hawley" <warthog19@eaglescrag.net>,
"Junio C Hamano" <gitster@pobox.com>,
"Lars Hjemli" <hjemli@gmail.com>
Subject: Re: Gitweb caching: Google Summer of Code project
Date: Fri, 30 May 2008 18:04:40 +0200 [thread overview]
Message-ID: <b77c1dce0805300904o5b4363efkc4591fc820164bf7@mail.gmail.com> (raw)
In-Reply-To: <20080530153822.GH593@machine.or.cz>
2008/5/30 Petr Baudis <pasky@suse.cz>:
>
> Wow, and here I was wondering if requiring at least 5.6 was not too
> liberal. ;-) I believe 5.8 is the newest possible candidate though, it
> is still too widespread; e.g. Debian-wise, many servers run on Etch and
> are going to stay there even for quite some time after Lenny gets
> released. Heck, I still have accounts on plenty of Sarge machines. ;-)
> (Sarge seems to have Perl-5.8.4.)
I think 5.8.2 is a good _minimum_ perl to support. Before that one,
Unicode support is next to null (5.6 and below) or too buggy, and
gitweb needs that.
next prev parent reply other threads:[~2008-05-30 16:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-27 18:03 Gitweb caching: Google Summer of Code project Lea Wiemann
2008-05-27 21:53 ` Jakub Narebski
2008-05-27 22:54 ` Lea Wiemann
2008-05-28 12:14 ` Jakub Narebski
2008-05-28 18:33 ` Lea Wiemann
2008-05-29 23:27 ` Jakub Narebski
2008-05-30 7:24 ` Lea Wiemann
2008-05-30 10:02 ` Jakub Narebski
2008-05-30 14:59 ` Lea Wiemann
2008-05-30 15:07 ` Petr Baudis
2008-05-30 15:27 ` Lea Wiemann
2008-05-30 15:38 ` Petr Baudis
2008-05-30 16:04 ` Rafael Garcia-Suarez [this message]
2008-05-30 18:56 ` J.H.
2008-05-30 20:28 ` Junio C Hamano
2008-05-30 21:32 ` Lea Wiemann
2008-05-30 18:47 ` Lea Wiemann
2008-05-31 10:15 ` Jakub Narebski
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=b77c1dce0805300904o5b4363efkc4591fc820164bf7@mail.gmail.com \
--to=rgarciasuarez@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=hjemli@gmail.com \
--cc=jnareb@gmail.com \
--cc=lewiemann@gmail.com \
--cc=pasky@suse.cz \
--cc=warthog19@eaglescrag.net \
/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).