To work on a different issue, you need a different branch. Rebasing just updates your repo with respect to the remote one. To create a new branch, first goto master- git checkout master Then create new branch- git checkout -b new_branch_name
Now you can work on your issue, and this branch won't have the commits of your earlier branch. Never do 'git checkout -b' from a branch other than master. On Friday, February 22, 2013 5:39:23 PM UTC+5:30, Manoj Kumar wrote: > > Hello Everyone, > > I need some basic help in git. > > Suppose I have a branch 1001. I've made changes in it, commited and sent a > pull request. However the commits are yet to be merged. So there is a good > possibility that it might get a bad review and I'll need to make a few > changes. Since the review process, takes quite some time, I would like to > work on another issue till then. > > So according to the development workflow, this is what I have to do. > > git checkout master > > git pull > > git checkout 1001_issue > > git rebase master. > > This (which I guess) changes my local repository, so that the commits are > present in the local repository. However when I start a new branch, I don't > want my old commits to be there, just in case they are faulty. What is the > best way to overcome this? > > > > > > -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
