Manoj Govindan wrote:
Another solution that you could do is ssh to a site outside of the proxy, do the svn checkout on the remote host, and simply rsync the tree to your local computer. If you want to update to latest, just ssh back to the remote host, do an svn up, and rsync again.Is there a way to check out the latest version of Django code using the svn+ssh mechanism? svn co svn+ssh://code.djangoproject.com/svn/django/trunk/django
I personally recommend going the git route. It is very helpful in my personal projects. It also makes it easy to manage patched checkouts of django. First I cloned the django repo, then created a branch, applied a patch for an ldap authentication backend, and committed the patch to my local branch. git keeps django current, and is smart enough to reapply the patch to the newer revisions.
Good luck! Jeff Anderson
signature.asc
Description: OpenPGP digital signature
