ti., 11.05.2010 kl. 02.36 -0700, skrev smichr: > > > As I already said, it would be much easier if you could create another > > > branch for review (1766-for-review) which contains only "stable" changes. > > > This would help to get it in faster. > > The commits before "1766----------------------" are stable. I am not > changing those. I am only, as review is received adding changes that > will be squashed into them. They are ready for review. > > The problem with assigning each one to its own branch is that when > they need to be rebased it becomes a rebase headache. Is there an > easier way to rebase several branches? If the turn-around for review > were days this would not be an issue but it takes much longer than > this. To me the situation seems ideal: I have all the unpushed work at > my disposal; it's all rebasable in one branch; and cherry-pickable by > anyone who wants to grab a commit for review. > > Is there a reason that this is difficult or is it that you aren't sure > if that review is stable or not? As for the latter: the numbered > commits before 1766 are stable. >
I hope I am not adding confusion here, but I think Vincent just asked for something like ]$ git branch 1766-for-review ff50ca5221a22e9b80d1 Øyvind -- 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.
