* Aaron Bannert wrote:
> On Thursday, May 29, 2003, at 12:30 PM, [EMAIL PROTECTED] wrote:
>
>> Modified: docs/manual Tag: APACHE_2_0_BRANCH bind.html.en
>> bind.html.ja.jis bind.html.ko.euc-kr
>> cgi_path.html.en cgi_path.html.ja.jis
>> cgi_path.html.ko.euc-kr configuring.html.en
> [...]
>
> I've been trying to hold my tongue on this, but I can't any longer.
> Is there something we can do about gigantic commits like this? This
> commit generated a 660KB email! Nobody is reading these emails. I'm
> already opposed to having automatically generated content committed
> to CVS, but when I'm receiving gigantic emails like this it's too much.
Hmmmmm, sorry.
I'd see some alternatives
- split the commit (e.g. by language)
- create a new docs-cvs-mailinglist
- drop the generated files and build the stuff online and for every release
(RM job, resp. the tarball roller's) - would need some MBs of Java stuff
installed everywhere
- ?
The first item seems to me currently the best... Other suggestions are
welcome :-)
nd
--
my @japh = (sub{q~Just~},sub{q~Another~},sub{q~Perl~},sub{q~Hacker~});
my $japh = q[sub japh { }]; print join #########################
[ $japh =~ /{(.)}/] -> [0] => map $_ -> () # Andr� Malo #
=> @japh; # http://www.perlig.de/ #
