On Thursday, May 29, 2014 7:00:52 PM UTC+1, William wrote: > > The argument that mailing patches "doesn't work at that scale" isn't > convincing, since Linux kernel development is much bigger than Sage > development, and they mail patches around
That is not really true. They do mail patches around, but only at one very specific point in the lifetime of a changeset. The entire model is geared towards making everything as easy as possible for Linus. You present your change in a way that is as easy as possible for one of the inner circle to look at, and then forward to Linus. They don't collaborate with you, the only feedback is that your code is merged or refused (likely before it ever reaches Linus). Since it is a one way road its of course easier to mail a patch. The way I see it that does make it more difficult for the developers outside of the inner circle, they will have to resolve conflicts in their own branches whenever a new version appears. But that is parallelizable and developers are experienced with the tools, so its not a problem for the kernel. -- 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.
