Yo ! > Its not just me, ask any lager project that is using git. Half of them even > force you to clean up your history before submitting anything.
Volker, I am not telling you that having bad histories is good, I am telling you that letting newcomers not care about the amount of merge commits is not a problem for us. We already do that to some extent: when I see a newcomer here I make very very long reviews about all points of doc and doctests, and from time to time I do these changes myself telling them what he should pay attention to. That is normal. I remember having refused to review a patch because the history was awful, and this is something I did because the reviewer was experienced. So let us insist on having clear histories, because indeed, like the code, "history is read much more often than it is written", but that is not such a big problem if the first 2~3 patches of a newcomer have one or two commit merges. Again, you only create a merge commit when the development of a ticket lasts over several beta releases, and in my experience this is rare for newcomers. Newcomers patches are never fundamental stuff, and this will not be a problem in the long run. So even if it is just to prevent them from recompiling Sage when they want to fix a typo in the doc, let's make it easy for them. If they stick around they will get to learn git anyway. Nathann -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
