Hello, Should the work us SoC'ers do this summer constantly pull from the master so merging back at the end isn't a hassle? I was nailed for that a few years back and as a result the code never made it back in.
Cheers On Thu, Apr 29, 2010 at 4:32 PM, Ondrej Certik <[email protected]> wrote: > Hi, > > I just found out this: > > http://github.com/certik/sympy/network > > it nicely shows patches from other people, one can nicely see which > branches are not yet merged in, as well as to see some patch > description by pointing the mouse to some dot. > > E.g. I can nicely see that the following people have branches that > should be merged in after review: > > * smichr > * rlamy > * haz > > Maybe we can use this for tracking patches. > > Ondrej > > -- > 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] <sympy%[email protected]>. > For more options, visit this group at > http://groups.google.com/group/sympy?hl=en. > > -- 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.
