Am 23.11.11 02:54, schrieb Rob Weir:
On Tue, Nov 22, 2011 at 6:49 PM, Kay Schenk<[email protected]> wrote:
Folks--
I have been doing some cleanup/fixing of the OOo legacy site as we're
transporting to ooo-site.apache.org.
The legacy site is QUITE large, and because of the more or less single
trunk we have now, much of what I'm doing will no doubt affect your local
repository sizes. So, if you do an update soon, you will definitely notice
this.
Nearly all of the legacy projects sites were incomplete with only one level
of information whereas most contain many sub-directories -- this is what
I'm trying to fix.
Monday and Tues, the following areas were fixed with the following sizes by
directory:
qa: 679M
api: 196M
documentation: 2.3G
dba: 37M
bibliographic: 48M
Hopefully by this coming Sunday, barring an unforeseen issues, I will also
"fix" (update) the following areas:
external: 1.6M
framework: 27M
graphics: 3.3M
gsl: 5.2M
ui: 571M
marketing: 1.6G
xml: 41M
ux: 170M
tools: 359M
udk: 69M
ucb: 864K
installation: 975M
lingucomponent: 11M
porting: 19M
sc: 80M
sw: 170K
You'll want to check with Infra@ for how much the SVN sync can take at
once. My guess is these large chunks (975M, etc.) will need to be
broken up into smaller commits.
Yes, that's true. The SVN is mirrored, and if the pieces are too big,
the svn mirror has no chance to update. This make trubble.
Greetings Raphael
--
My private Homepage: http://www.raphaelbircher.ch/
