Jo, Please stop derailing the conversation and answer our questions. In particular, answer Ondrej's question:
> So this should be our recommendation. Jason already agreed to the above. Yo and others, do you also agree with the above? You are so focused on finding minor counter arguments to minor details that you are wasting all of our time and energy. The more you do this, the less we like you. We are trying to solve a problem and you are bogging that down. Very little of what you have written, if anything at all, has helped us solve the problem at hand. I'm not sure you can even state the problem because you are so focused on defending the details of rebasing. All I can gather is that you want us to encourage and promote rebasing which is the exact opposite of this proposed guideline. All of us believe that the overhead of rebasing is too high. We are willing to give up the minor benefits of a superbly clean git log to ensure that we have minimal overhead for contributions. Let me repeat, "you can still rebase your PR if your reviewers agree" and "if absolutely necessary you can submit a new 'clean' PR". Can we move forward here and close this thread? It is obvious that you want the last word and that you believe your personal needs and opinions trump that of the groups. This kind of behavior is not productive and is not gaining you any allies. You should seriously think deeply about this and think about changing your behavior. Jason moorepants.info +01 530-601-9791 On Thu, Jul 16, 2015 at 1:57 AM, Joachim Durchholz <j...@durchholz.org> wrote: > Am 16.07.2015 um 05:32 schrieb Aaron Meurer: > >> Also, if you're a habitual rebaser and you have push access, you had >> better >> have your origin remote set to read-only. >> > > Very much agreed. > Maybe not just for habitual rebasers, merging with conflicts can go wrong, > too. > > I hope to set up my own projects so that committers will have two > workdirs, one for day-to-day work preparing PRs and one for working on the > main branch. > The former can have its push access disabled; for the latter, I hope > there's a way to disable rebasing and merge conflict resolution. > > -- > 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 sympy+unsubscr...@googlegroups.com. > To post to this group, send email to sympy@googlegroups.com. > 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/55A77213.1070709%40durchholz.org. > > For more options, visit https://groups.google.com/d/optout. > -- 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 sympy+unsubscr...@googlegroups.com. To post to this group, send email to sympy@googlegroups.com. 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/CAP7f1AgpBgxsG74Y_JhwW88xvBEMqRSBVxML19FGZJeL1Pce2g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
