On Sun, Jun 17, 2012 at 12:35 AM, Aaron Meurer <[email protected]> wrote: > On Jun 16, 2012, at 3:29 PM, Sergiu Ivanov <[email protected]> wrote: > >> On Sun, Jun 17, 2012 at 12:24 AM, Aaron Meurer <[email protected]> wrote: >> >>> Rebasing can also have other issues, like removing almost all of a >>> commit, making it no longer do what the commit message says it does >>> (which can be very confusing to someone looking at the commit later). >> >> That's right; I'd rewrite the commit message then, which isn't much of >> a trouble to me. > > The problem is that with big branches, they can sneak in without > warning. You essentially have to review each commit after rebasing to > make sure it didn't happen, because git automatically "rebases out" > stuff without warning.
Oh, I see; I didn't get that from the first time, thank you! >> I guess I'm some sort of weird rebase fan, that's why my question :-) > > Well then we picked the right GSoC mentor for you :) Hmm :-) This gives me additional insight about Tom's preferences ;-) Sergiu -- You received this message because you are subscribed to the Google Groups "sympy" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sympy?hl=en.
