On Wed, Oct 27, 2010 at 4:24 PM, Ondrej Certik <ond...@certik.cz> wrote: > On Tue, Oct 26, 2010 at 4:54 PM, William Stein <wst...@gmail.com> wrote: >> Hi, >> >> I just spent the day working on code with some people, and using >> http://code.google.com with multiple cloned repositories and their >> code review system, which allows excellent line by line annotation, >> allows much better viewing of file diffs, etc., is really much, much >> better than what we do with trac and the sage referee process. I >> know Robert Bradshaw and Craig Citro have been saying this for a long >> time, but I want to add that they are so, so right. > > I think that the best review system currently is the github pull request > system: > > http://help.github.com/pull-requests/ > > for example for sympy: > > http://github.com/sympy/sympy/pulls > > and click on the "Closed" button to see all the already integrated > pull requests.
That's a very nice model. I wonder if it would scale now--"you have 250 pull requests..." Google code has the ability for people to "fork" and pull changes back and forth, but I'm not sure if it's as refined. One nice thing about git is that it's easier to selectively pull portions of a repo. Certainly better than manually passing patches through trac in any case. - Robert -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
