All:

Is it ok if I remove old Cocoon releases from the xml.apache.org?
To be precise:

cocoon-1.7.x
cocoon-1.8
cocoon-2.0
cocoon-2.0.1
cocoon-2.0.2
cocoon-2.0.3


Vadim


-------- Original Message --------
Subject: need some more web space conservatism again
Date: Wed, 22 Jan 2003 18:02:49 -0800 (PST)
From: Brian Behlendorf <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
CC: [EMAIL PROTECTED], "" <[EMAIL PROTECTED]>, "" <[EMAIL PROTECTED]>, "" <[EMAIL PROTECTED]>



We're at 98% on /x2 on daedalus.

daedalus# pwd
/x2/www
daedalus# du -s *
1985 ant.apache.org
17507 apr.apache.org
1 avalon.apache.org
291 bugs.apache.org
10 commons.apache.org
1 db.apache.org
1 default
360518 dev.apache.org
188695 httpd.apache.org
1260 incubator.apache.org
9050781 jakarta.apache.org
169331 java.apache.org
132990 perl.apache.org
162729 search.apache.org
3259 tcl.apache.org
1723597 www.apache.org
3882678 xml.apache.org

daedalus# du -s */builds
7309216 jakarta.apache.org/builds

Could we get a general clean-sweep through there from all projects,
looking for old pages that can be deleted, etc? And in particular, can
the Jakarta build maintainers clean some things up? I see full builds
being kept of every minor release and beta version of some apps like
Tomcat.... I don't want to start calling people names....

Brian





---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to