On Thu, Jul 16, 2009 at 9:19 PM, Bill Hart<[email protected]> wrote: > > Yes, that is my plan. At present I have access to zero machines with a > web server and git-svn installed. So I can't do this at present. > > I don't know how easy it would be to automatically track the svn repo. > One way is to have a screen session in which a script runs keeping it > up-to-date.
If the svn server runs the same machine as the git server, I think you could use a post-commit hook in the svn repo so that the git-svn is run immediately. >> This assumes that cloning a git repo is faster than starting the svn >> --> git cloning... (not hard, given how awfully slow svn alone >> already is). > > Yes, Git cloning should be extremely fast. Everything Git related is. > It was designed for extremely high performance. I know, git is faaaast... I just wanted to rant about how bad svn is performancewise... (you try it under high roundtrip latency... mine right now is 500 ms to www.google.com and 600 ms to sage.math.washington.edu, auch!) Gonzalo --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "mpir-devel" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/mpir-devel?hl=en -~----------~----~----~----~------~----~------~--~---
