Instead of creating new branches every time you update your repo I suggest using stgit [0]. You should be careful though because you can mess up and overwrite things, but as long as you are the person pulling and pushing to your repo this will allow for easier changes.
-- Andy [0] http://www.procode.org/stgit/doc/tutorial.html On Wed, Jun 9, 2010 at 3:07 PM, jegerjensen <jensen.oyv...@gmail.com> wrote: > Sorry, I didn't know about the tests under doc/. I fixed it in the > second patch, and created new branches at github: > http://github.com/jegerjensen/sympy/tree/fortran_codegen2 and > http://github.com/jegerjensen/sympy/tree/fortran_free_form3 . > > -- > You received this message because you are subscribed to the Google Groups > "sympy-patches" group. > To post to this group, send email to sympy-patc...@googlegroups.com. > To unsubscribe from this group, send email to > sympy-patches+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/sympy-patches?hl=en. > > -- You received this message because you are subscribed to the Google Groups "sympy-patches" group. To post to this group, send email to sympy-patc...@googlegroups.com. To unsubscribe from this group, send email to sympy-patches+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sympy-patches?hl=en.
