Hi Daniel, On Tuesday, 2011-08-16 20:03:38 +0300, Daniel Shahaf wrote:
> > I'm assuming that on the Infra side, they would first lock SVN from > > writes, do a dump of the existing AOOo repository, as a backup, then > > load my dump file. That way, if anything goes wrong, they can restart > > from a known state. > > Essentially, yes. Except that there is no "AOOo repository" --- all of > /repos/asf is one repository. I noticed that when I initially did git svn clone "the ooo part of the repo", it took a while until it scanned the some 100000 revisions, and I thought that was for the incubator podlings' site/www/wiki only. But, is it really wise to have even the actual source code all in one repo? Given that AOOo will add 76k files and in future lots of change sets are to be expected, won't that affect the overall repo too much in the sense that it will add revisions for everyone not involved with AOOo code? Just thinking of future git svn clone approaches and the like. What's the reason to have all in one repository? Eike -- PGP/OpenPGP/GnuPG encrypted mail preferred in all private communication. Key ID: 0x293C05FD - 997A 4C60 CE41 0149 0DB3 9E96 2F1A D073 293C 05FD
pgps0kglNxpXf.pgp
Description: PGP signature
