I'm actually more of a fan of github branches, because they are easier to get (git fetch remote vs. download patch, git am patch, hope it works…).
By the way, you should clean up your github by deleting Ondrej's branches (everything except for master and your branches). You can do this by doing git push :branch-name github (assuming you have your github set up as a remote tracking branch named github). The colon before the branch name tells github to delete the remote branch. Of course, I am hardly one to talk about having a messy github (I have 84 branches up there…). :) Also, it's better to post the branch name, instead of the commit hash. I used git branch -r --contains bf41a9fef4ec4e92f0e984a8f5bdece6db058deb to figure out that it is in your implies-change branch, but it would have been easier if you had just posted that in the first place. Aaron Meurer On Mar 24, 2010, at 2:38 PM, Vinzent Steinberg wrote: > 2010/3/24 Christian Muise <christian.mu...@gmail.com> > I thought it went through...sorry about that. > - http://github.com/haz/sympy/commit/bf41a9fef4ec4e92f0e984a8f5bdece6db058deb > > I need to run, but I can submit the patch officially later today > (struggling with git still :p). > > git format-patch and git send-email are your friends. :) But a git branch is > also nice to review. > > Vinzent > > -- > 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.
