On Jun 14, 2010, at 3:24 PM, Brian Granger wrote: > Hi, > > I am getting back to sympy now that finals are done and I noticed that > the repo situation with sympy is a bit confusing: > > * There is now a sympy/sympy github repo, that looks very attractive > to fork and use... > * But it is not in sync with git.sympy.org. > > What is the plan for the github repo? Should we get rid of > git.sympy.org entirely? Should be get rid of the github repo? Is > there was to keep them in sync? Which do we recommend to new devs to > clone? You should clone from git.sympy.org and fork from github, as Christian said. We should probably setup the build bot to push changes up to github. For now, Ondrej gave write access to all the sympy developers who had a github account, so you should be able to just add sympy as a remote repository and do "git push sympy" to update it.
I think the idea behind the github sympy was to give people a repository to fork that would put them in the network, but wouldn't give them the junk branches that would come from forking, say, my repository instead. Aaron Meurer > > Cheers, > > Brian > > -- > You received this message because you are subscribed to the Google Groups > "sympy" 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/sympy?hl=en. > -- You received this message because you are subscribed to the Google Groups "sympy" 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/sympy?hl=en.
