I've extended the: test_euler.py
from Sergey's branch. Unfortunately I did not manage to send him back a push request of the performed changes, so I created a temporary gist here: https://gist.github.com/saullocastro/6495587 @Sergey, could you have a look if your module handles this type of functionals. If not I want to put the ideas of this: https://gist.github.com/saullocastro/6433919 Into your module. Thank you! 2013/9/9 Aaron Meurer <[email protected]> > The workflow I described is not the only way to do things, it's just > the way that we do things in this community (and most similar > communities on GitHub). But some projects use completely different > workflows (e.g., some projects push all their branches to the main > repo and don't use forks at all). > > The best thing is to try to understand what each of the git commands > does, clone, remote add, fetch, checkout, branch, push, etc. If you > understand what all the commands actually do, then doing anything in > git is just a matter of breaking what you want to do into the relevant > commands. > > Aaron Meurer > > On Sun, Sep 8, 2013 at 1:06 AM, Saullo Castro <[email protected]> > wrote: > > @Aaron, thank you very much for the explanation. I would have taken much > > longer to achieve this alone... we should post this as a question in > > StackOverflow since I haven't found it there so far... > > > > > > 2013/9/7 Aaron Meurer <[email protected]> > >> > >> The workflow is that you clone a repo once, from the official github > >> (so in this case, sympy/sympy), and you add forks (including your own) > >> as remotes. So, if you haven't cloned yet > >> > >> git clone [email protected]:sympy/sympy.git > >> cd sympy > >> > >> then add skirpichev as a remote > >> > >> git remote add skirpichev [email protected]:sympy/sympy.git > >> > >> and download the code > >> > >> git fetch skirpichev > >> > >> and check out the code > >> > >> git checkout skirpichev/3198-euler > >> > >> This will checkout a "detached head" state. If you want to commit > >> additional changes to the remote branch, you need to create your own > >> branch. > >> > >> git branch branchname > >> > >> By the way, you can replace the ssh urls with https or git urls if you > >> want. It's recommended to use ssh for your own fork, though, if your > >> network allows it, because it's much easier and more secure. > >> > >> Once you do have your own fork, you can do > >> > >> git remote add github [email protected]:yournick/sympy.git > >> > >> (replace "yournick" with your nickname). > >> > >> The names of the remotes are arbitrary, but it's easiest if you use > >> "github" for your fork and the person's username for other people's > >> forks. > >> > >> Then, to push code to your fork, use > >> > >> git push github branchname > >> > >> Aaron Meurer > >> > >> On Sat, Sep 7, 2013 at 3:26 AM, Saullo Castro <[email protected]> > >> wrote: > >> > I created a fork of sympy in my account. > >> > Now I don't know which branch to add in order to get this pull > request. > >> > For this case, which name should I use for github-somenick ? And for > >> > somebranch. > >> > > >> > Sorry by these basic questions, but I have really no idea ! > >> > > >> > > >> > > >> > On Saturday, September 7, 2013 11:12:38 AM UTC+2, Sergey Kirpichev > >> > wrote: > >> >> > >> >> On Sat, Sep 07, 2013 at 10:13:01AM +0200, Saullo Castro wrote: > >> >> > I tried to clone�[1]https://github.com/sympy/sympy/pull/2431 > �but > >> >> > this > >> >> > is > >> >> > not merged yet. How can I clone from this pull request in order > to > >> >> > work in > >> >> > it? > >> >> > >> >> Clone sympy first. Then, add remote repository you needed: > >> >> git remote add github-somenick [email protected]:somenick/sympy.git > >> >> git fetch github-somenick > >> >> > >> >> and check out the branch you want to work on: > >> >> git checkout -b you-name-it github-somenick/somebranch > >> >> > >> >> PS: > >> >> Inspired by: > >> >> > >> >> > >> >> > https://github.com/sympy/sympy/wiki/Development-workflow#wiki-cloning-sympy > >> > > >> > -- > >> > You received this message because you are subscribed to the Google > >> > Groups > >> > "sympy" group. > >> > To unsubscribe from this group and stop receiving emails from it, send > >> > an > >> > email to [email protected]. > >> > To post to this group, send email to [email protected]. > >> > Visit this group at http://groups.google.com/group/sympy. > >> > For more options, visit https://groups.google.com/groups/opt_out. > >> > >> -- > >> You received this message because you are subscribed to a topic in the > >> Google Groups "sympy" group. > >> To unsubscribe from this topic, visit > >> https://groups.google.com/d/topic/sympy/cvOjJdEWprM/unsubscribe. > >> To unsubscribe from this group and all its topics, send an email to > >> [email protected]. > >> > >> To post to this group, send email to [email protected]. > >> Visit this group at http://groups.google.com/group/sympy. > >> For more options, visit https://groups.google.com/groups/opt_out. > > > > > > -- > > You received this message because you are subscribed to the Google Groups > > "sympy" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to [email protected]. > > To post to this group, send email to [email protected]. > > Visit this group at http://groups.google.com/group/sympy. > > For more options, visit https://groups.google.com/groups/opt_out. > > -- > You received this message because you are subscribed to a topic in the > Google Groups "sympy" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/sympy/cvOjJdEWprM/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/sympy. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "sympy" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sympy. For more options, visit https://groups.google.com/groups/opt_out.
