On Thu, Jul 16, 2009 at 3:11 AM, Bill Hart<[email protected]> wrote: > Another option, which will be faster, is to clone someone else's git > repository, > though if you want to keep up with the central svn repo, you will have to > wait > for them to rebase before you can get the updates from them every time. That > won't be a problem if you are working with a group of people on MPIR, as only > one of you will need to stay up to date with the svn repo and the rest can > just rip from them. Otherwise you will have to wait, just this once, for Git > to get all the (thousands of) recent revisions from the central svn repo.
Can you eventually set up a "public" git repository which just tracks the central svn repo. This way one can checkout from scratch with git, without the need for the painful conversion... (i.e. my proposal is that "only one of you will need to stay up to date with the svn repo" be a public service, which *only* tracks the svn repo). 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). 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 -~----------~----~----~----~------~----~------~--~---
