I am clearly doing this wrong. There must be a more-efficient way to handle this than by an SVN check-out and, after the check-out is interrupted for some reason, subsequent SVN updates to continue pulling down a working copy of the repo, rinse-repeat whenever there are connection failures of some kind.
I say that because I am around 12 hours into that process and I am still pulling just the trunk (at about 1.5 GB including all of the .svn stuff). Fortunately, it doesn't swamp my machine and I can do other work, such as write emails [;<). Don't think I'll try watching Netflix on-line though [;<). - Dennis PS: I have, since June 1, had a lifetimes supply of ways to show myself how stupid I am. Walking onto a project of this magnitude without first learning the toolcraft and customs on something smaller is not thrilling. I am going to find those smaller things to teeth on while I watch in horror how complex this activity is. -----Original Message----- From: Dennis E. Hamilton [mailto:[email protected]] Sent: Wednesday, August 24, 2011 16:22 To: [email protected] Subject: RE: Update on SVN dump load Ah, the excitement builds ... One way to not do commits (and to avoid certificate warnings) is to use the http:// address, not the https:// form. - Dennis -----Original Message----- From: Rob Weir [mailto:[email protected]] Sent: Wednesday, August 24, 2011 15:17 To: [email protected] Subject: Update on SVN dump load Our JIRA issue has been updated: https://issues.apache.org/jira/browse/INFRA-3862 Joe has done a test load onto: https://svn-master.apache.org/repos/test/joes/ooo No commits to it, please, but yell out if you see anything wrong. It looks good so far. -Rob
