[replying to maillist instead of issue tracker] > <https://github.com/cbm755>I've noticed that you rebase a lot. Rebasing after code is "public" is not a great > habit to get into. Check our dev workflow ...
Thanks for this. From the dev workflow doc: > The only time when it is recommended to rebase instead of merge is when you > need to edit your commit messages, or **remove unnecessary commits**. Would this latter case include cleaning up a (sordid) history that has approaches tried but latter reverted? For example in pr #7824, I had some low-level changes to superclasses that are later reverted. Otherwise, strikes me as messy to have that sort of thing in the history of master... thanks, Colin -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/sympy/c94ed790-6016-4e26-a562-e778cb70d412%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
