Am 01.10.2014 um 22:46 schrieb Colin Macdonald:
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...
Things get messy for others if they merge your work into their own changes - they will need to rebase their work, too.
As long as you put up your updates with an explicit "don't merge" tag, it's fine (except that github discussions will get lost, which is not-so-nice; you should summarize these discussions in comments in the rebased code, but this still isn't *that* optimal).
A messy history isn't *that* much of an issue. We mostly need it for bisecting, and possibly to trace back a decision (in which case we'll want to look at the discussions again).
HTH Jo -- 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/542CEB7A.3000702%40durchholz.org. For more options, visit https://groups.google.com/d/optout.
